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.
CVE-2026-76852
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 17, 2026
Advisory Details (2)
Auto-updated Sep 15, 2026Netcore NR268 1.7.121109 Forgeable Firmware Authenticity Check in mtd_write | Advisories | VulnCheck
https://www.vulncheck.com/advisories/netcore-nr268-1.7.121109-forgeable-firmware-authenticity-check-in-mtd-writenetcore-router-public-refs/2026.08.19-netcore-nr268-firmware-forgery.md at main · draw-ctf/netcore-router-public-refs · GitHub
https://github.com/draw-ctf/netcore-router-public-refs/blob/main/2026.08.19-netcore-nr268-firmware-forgery.mdVendor Advisories for CVE-2026-76852(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 04:22 UTCEG score recompute
- 2026-09-19 04:22 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 16:55 UTCGHSA enrichment
- 2026-09-18 05:28 UTCEG score recompute
- 2026-09-18 05:28 UTCGHSA enrichment
- 2026-09-17 18:01 UTCEG score recompute
- 2026-09-17 18:01 UTCGHSA enrichment
- 2026-09-17 07:21 UTCGHSA enrichment
- 2026-09-16 19:53 UTCEG score recompute
- 2026-09-16 19:53 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 09:47 UTCEG score recompute
- 2026-09-16 09:47 UTCGHSA enrichment
- 2026-09-15 22:19 UTCEG score recompute
- 2026-09-15 22:04 UTCEG score recompute
- 2026-09-15 22:02 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-76852?
When was CVE-2026-76852 disclosed?
Is CVE-2026-76852 actively exploited?
What is the CVSS score of CVE-2026-76852?
How do I remediate CVE-2026-76852?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76852
Is Your Infrastructure Affected by CVE-2026-76852?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.