CVE-2026-21039

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
6.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Improper access control in Settings prior to SMR Jul-2026 Release 1 allows local attackers to configure Theft protection settings.

CVSS v3
6.9
EG Score
6.9(medium)
EPSS
1.3%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 10, 2026

Advisory Details (1)

Auto-updated Jul 10, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-21039(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 20× in last 7d / 20× 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.

  1. 2026-07-15 21:16 UTCEG score recompute
  2. 2026-07-15 21:16 UTCGHSA enrichment
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-14 22:36 UTCEG score recompute
  6. 2026-07-14 22:36 UTCGHSA enrichment
  7. 2026-07-13 23:56 UTCEG score recompute
  8. 2026-07-13 23:56 UTCGHSA enrichment
  9. 2026-07-13 22:30 UTCEPSS rescore
  10. 2026-07-13 01:16 UTCEG score recompute
  11. 2026-07-13 01:16 UTCGHSA enrichment
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-12 02:36 UTCEG score recompute
  15. 2026-07-12 02:35 UTCGHSA enrichment
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-11 03:55 UTCEG score recompute
  18. 2026-07-11 03:55 UTCGHSA enrichment
  19. 2026-07-10 05:15 UTCEG score recompute
  20. 2026-07-10 05:13 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-21039?
CVE-2026-21039 is a medium vulnerability published on July 10, 2026. Improper access control in Settings prior to SMR Jul-2026 Release 1 allows local attackers to configure Theft protection settings.
When was CVE-2026-21039 disclosed?
CVE-2026-21039 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-21039 actively exploited?
CVE-2026-21039 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-21039?
CVE-2026-21039 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-21039?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-21039, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-21039

Explore →

Is Your Infrastructure Affected by CVE-2026-21039?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.