Secuno
ENNL
Book demo

CVE-2026-76852

8.8 HIGHEPSS 0.23%
  1. Published15 Sept 2026

Description

Netcore NR268 firmware version 1.7.121109 has an improper integrity verification flaw in mtd_write allowing forged firmware authenticity checks. Attackers can exploit put_file.cgi and check_image_uuid.c to bypass firmware signature validation and load unauthorized firmware images.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-927019.1
trusted execution environments. In versions up to and including 0.8.2, the…
CVE-2026-541748.3
melange allows users to build apk packages using declarative pipelines. Apko prior to…
CVE-2026-825498.3
A vulnerability was identified in Linux Foundation Magma 1.9.0. This affects an unknown…
CVE-2026-758039.1
Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can…
CVE-2026-756259.0
Kraken agents fail to verify peer-to-peer downloaded blobs against their requested…
CVE-2026-128178.6
In Bouncy Castle for Java before 1.85, OpenPGP AEAD decryption skips final tag on…

Frequently asked

Is CVE-2026-76852 being actively exploited?

CVE-2026-76852 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.23%.

How severe is CVE-2026-76852?

CVE-2026-76852 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.23% probability of exploitation.

How do I fix CVE-2026-76852?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-76852 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.