CVE-2026-102700

MEDIUMPre-NVD 4.74.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 4.7 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1% (4th 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, EPSS

Also known asEUVD-2026-98832 (ENISA EUVD) · GHSA-hwfh-h726-49f6 (GitHub Security Advisories)Source: ENISA EUVD

4.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

With its original introduction, GNTTAB_cache_flush was made available uniformly. XSA-232 (CVE-2017-14318) then covered an omitted NULL pointer check, yet the addition of that check failed to adjust the subsequent error path. That error path fails to drop a page reference in case the specified page is owned by a special system domain (DOM_IO and DOM_COW are system domains which can have memory pages assigned to them.)

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
21
EG Risk 21/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)
Severity47% × 45%
Impact severity (EG Severity): CVSS 4.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
4th
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 (4.7): severity, escalated by confirmed exploitation. This CVE's 4.7 is its impact severity (EG Severity), not escalated.

EG Severity
4.7 MEDIUMCVSS-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.1% 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

October 13, 2026

Last Modified

October 20, 2026

Advisory Details (2)

Auto-updated Oct 20, 2026
Patch available.
Web page

XSA-520 - Xen Security Advisories

http://xenbits.xen.org/xsa/advisory-520.html
Web page

XSA-520 - Xen Security Advisories

https://xenbits.xenproject.org/xsa/advisory-520.html

Vendor Advisories for CVE-2026-102700(1)

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

Affected Packages

(6 across 6 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.19.6-r2: fixed in 4.19.6-r2
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.20.4-r2: fixed in 4.20.4-r2
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.20.4-r2: fixed in 4.20.4-r2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
xen4.17.1+2-gb773c48e36-1 ... 4.17.7-0+deb12u1 (15 versions)
  • every version up to 4.17.7+13-g2445b30a44-0+deb12u1: fixed in 4.17.7+13-g2445b30a44-0+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
xen4.20.0+68-g35cb38b222-1 ... 4.20.3+127-gc42374a105-1 (8 versions)
  • every version up to 4.20.4+39-gf1e1321c87-0+deb13u1: fixed in 4.20.4+39-gf1e1321c87-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
xen4.20.0+68-g35cb38b222-1, 4.20.2+37-g61ff35323e-1, 4.20.2+7-g1badcf5035-1, 4.20.2+7-g1badcf5035-2, 4.20.3+127-gc42374a105-1
  • every version up to 4.20.4+39-gf1e1321c87-1: fixed in 4.20.4+39-gf1e1321c87-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 32× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  2. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  3. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  4. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  5. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  6. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  7. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  8. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  9. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  10. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  11. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-25 14:56 UTCEchelonGraph re-scored
  20. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-10-20 18:27 UTCGHSA enrichmentGHSA-hwfh-h726-49f6
  24. 2026-10-20 17:22 UTCEchelonGraph re-scoredFirst assessed: 4.7 MEDIUM
  25. 2026-10-20 17:22 UTCGHSA enrichmentGHSA-hwfh-h726-49f6
Show 14 more
  1. 2026-10-20 17:21 UTCMITRE cvelistV5CVSS v3 → 4.7 · severity → MEDIUM
  2. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  3. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  4. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  5. 2026-10-18 05:10 UTCEchelonGraph re-scored
  6. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-10-14 18:45 UTCEchelonGraph re-scored
  10. 2026-10-14 18:45 UTCGHSA enrichmentGHSA-hwfh-h726-49f6
  11. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-13 16:25 UTCNVD update
  13. 2026-10-13 15:56 UTCEchelonGraph re-scored
  14. 2026-10-13 15:54 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)· as of November 12, 2026

Frequently asked(5)

What is CVE-2026-102700?
CVE-2026-102700 is a medium-severity vulnerability; its CVE record was published on October 13, 2026. With its original introduction, GNTTAB_cache_flush was made available uniformly. XSA-232 (CVE-2017-14318) then covered an omitted NULL pointer check, yet the addition of that check failed to adjust the subsequent error path. That error path fails to drop a page reference in case the specified page…
When was CVE-2026-102700 made public?
CVE-2026-102700 was made public on October 13, 2026: that is the date its CVE record's CNA, Xen Project, gives for when the vulnerability was made public. The CVE record itself was published on October 13, 2026. EchelonGraph's copy of the record carries a last-modified date of October 20, 2026; the record at its source may have been updated since.
Is CVE-2026-102700 actively exploited?
CVE-2026-102700 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102700?
CVE-2026-102700 has a CVSS v3.1 base score of 4.7 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-102700?
A fix for CVE-2026-102700 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102700 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-102700

Explore →

Is Your Infrastructure Affected by CVE-2026-102700?

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

Book a Demo →Browse All CVEs