CVE-2026-59045

HIGHPre-NVD 7.47.4
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.4 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.3% (18th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1
Trending — 6 sources updated this week

Also known asEUVD-2026-115446 (ENISA EUVD) · GHSA-gj9p-f54m-pq57 (GitHub Security Advisories)Source: ENISA EUVD

7.4EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.4Exploit: None knownExposed services: Not assessed

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

In multiple locations, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS v3
7.4
EG Score
7.4HIGHlow confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 2, 2026

Last Modified

November 3, 2026

Advisory Details (9)

Auto-updated Nov 3, 2026
No fix on record yet.
Web page

f6510cfbc728061d7a8d4ea4ac91e5fc270aaf6b - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/f6510cfbc728061d7a8d4ea4ac91e5fc270aaf6b
Web page

f0a2d3087b73b442b69fe0a9617ab920400abe15 - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/f0a2d3087b73b442b69fe0a9617ab920400abe15
Web page

eb970aae88c0f45056f4501b7815a9b5c7ab0435 - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/eb970aae88c0f45056f4501b7815a9b5c7ab0435
Web page

e10fb80c80387aa1f26695b57df95afe0ef00481 - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/e10fb80c80387aa1f26695b57df95afe0ef00481
Web page

c47ebb7427d5011de67b526eac67b42da640bdc5 - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/c47ebb7427d5011de67b526eac67b42da640bdc5
Web page

bd9aaec66cf50ea3ade2b537d9b730e40fe512e6 - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/bd9aaec66cf50ea3ade2b537d9b730e40fe512e6
Web page

acce19149cb8ebe92218d0e66c08bc36552ddbdf - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/acce19149cb8ebe92218d0e66c08bc36552ddbdf
Web page

22ae719f35b14f88e551f0e858a1087a4b721204 - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/22ae719f35b14f88e551f0e858a1087a4b721204
Web page

01ff2abe4905798e330a70f2970ee33a44419d24 - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/01ff2abe4905798e330a70f2970ee33a44419d24

Vendor Advisories for CVE-2026-59045(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 10× in last 7d / 10× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-11-03 16:28 UTCGHSA enrichmentGHSA-gj9p-f54m-pq57
  3. 2026-11-03 15:26 UTCEG score recomputeFirst assessed: 7.4 HIGH
  4. 2026-11-03 15:26 UTCGHSA enrichmentGHSA-gj9p-f54m-pq57
  5. 2026-11-03 15:26 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  6. 2026-11-03 15:08 UTCGHSA enrichmentGHSA-gj9p-f54m-pq57
  7. 2026-11-02 21:03 UTCENISA EUVD ID recordedEUVD-2026-115446 · Source: ENISA EUVD
  8. 2026-11-02 20:26 UTCNVD update
  9. 2026-11-02 20:02 UTCEG score recompute
  10. 2026-11-02 20:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59045?
CVE-2026-59045 is a high-severity vulnerability; its CVE record was published on November 2, 2026. In multiple locations, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
When was the CVE record for CVE-2026-59045 published?
The CVE record for CVE-2026-59045 was published on November 2, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2026; the record at its source may have been updated since.
Is CVE-2026-59045 actively exploited?
CVE-2026-59045 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59045?
CVE-2026-59045 has a CVSS v3.1 base score of 7.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-59045?
No fix for CVE-2026-59045 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-59045 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59045?

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