CVE-2026-128040

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreHIGH confidence

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

Score 6.1 from GitHub Security Advisory (severity: HIGH) published 2026-11-13. A secondary CVSS source baseline 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-125068 (ENISA EUVD) · GHSA-22hr-pg7v-x6hx (GitHub Security Advisories)Source: ENISA EUVD

6.1EG
EchelonGraph verdictMonitorNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; 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).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.1Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains a stored cross-site scripting vulnerability because admin pages render Dataflow profile link variables, tax rate titles, OAuth consumer names, and PayPal certificate filenames without escaping. An administrator restricted to one affected area can store script that runs when another administrator, including a full administrator, opens the page, reading the form key and performing actions with that administrator's privileges.

CVSS v3
6.1
EG Score
6.1MEDIUMhigh confidence
EG Risk
28
EG Risk 28/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)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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 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: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; 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
21st
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 (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). 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).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; 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 13, 2026

Last Modified

November 17, 2026

Advisory Details (6)

Auto-updated Nov 13, 2026
Fix referenced — no release confirmed yet. Sources: github, github_commit.
Web page

OpenMage magento-lts before 20.18.2 Stored XSS via Admin Dataflow, Tax, OAuth, PayPal Fields | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openmage-magento-lts-before-20.18.2-stored-xss-via-admin-dataflow-tax-oauth-paypal-fields
GitHub advisoryMentions a patch (unverified)

Admin-to-admin stored XSS via Dataflow status, tax rate title, OAuth consumer name and PayPal cert field · Advisory · OpenMage/magento-lts · GitHub

Affected: 21.0.0-beta3.

https://github.com/OpenMage/magento-lts/security/advisories/GHSA-m858-x59w-rmp5
GitHub commit

commit e97e257b8f8d (OpenMage/magento-lts)

Fix landed in OpenMage/magento-lts commit e97e257b8f8d — awaiting tagged release

https://github.com/OpenMage/magento-lts/commit/e97e257b8f8d74d2e52dbf28caa211c262ff26be
GitHub commit

commit d10314ddda9a (OpenMage/magento-lts)

Fix landed in OpenMage/magento-lts commit d10314ddda9a — awaiting tagged release

https://github.com/OpenMage/magento-lts/commit/d10314ddda9a6081bc27370b463b5f77c2e499de
GitHub commit

commit 7f7a9deaac11 (OpenMage/magento-lts)

Fix landed in OpenMage/magento-lts commit 7f7a9deaac11 — awaiting tagged release

https://github.com/OpenMage/magento-lts/commit/7f7a9deaac11fd2437bb1f8065db152a4b620609
GitHub commit

commit 62d2885fa6e7 (OpenMage/magento-lts)

Fix landed in OpenMage/magento-lts commit 62d2885fa6e7 — awaiting tagged release

https://github.com/OpenMage/magento-lts/commit/62d2885fa6e7a4454e3a5c7765a6a5ca0085ecc1

Vendor Advisories for CVE-2026-128040(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 9× in last 7d / 16× 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-21 16:38 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-11-20 05:40 UTCEchelonGraph re-scored
  4. 2026-11-20 05:40 UTCGHSA enrichmentGHSA-22hr-pg7v-x6hx · GitHub severity HIGH · GitHub CVSS 6.1
  5. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-11-17 20:29 UTCEchelonGraph re-scored
  8. 2026-11-17 20:29 UTCGHSA enrichmentGHSA-22hr-pg7v-x6hx · GitHub severity HIGH · GitHub CVSS 6.1
  9. 2026-11-17 19:49 UTCEchelonGraph re-scored
  10. 2026-11-17 19:49 UTCGHSA enrichmentGHSA-22hr-pg7v-x6hx · GitHub severity HIGH · GitHub CVSS 6.1
  11. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-11-16 16:49 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-11-15 16:57 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-11-14 16:39 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  16. 2026-11-13 15:49 UTCGHSA enrichmentGHSA-22hr-pg7v-x6hx · GitHub severity HIGH · GitHub CVSS 6.1
  17. 2026-11-13 12:55 UTCEchelonGraph re-scored
  18. 2026-11-13 12:55 UTCGHSA enrichmentGHSA-22hr-pg7v-x6hx · GitHub severity HIGH · GitHub CVSS 6.1
  19. 2026-11-13 10:30 UTCEchelonGraph re-scored
  20. 2026-11-13 10:01 UTCENISA EUVD ID recordedEUVD-2026-125068 · Source: ENISA EUVD
  21. 2026-11-13 09:38 UTCEchelonGraph re-scoredFirst assessed: 6.1 MEDIUM
  22. 2026-11-13 09:36 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-128040?
CVE-2026-128040 is a medium-severity vulnerability; its CVE record was published on November 13, 2026. OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains a stored cross-site scripting vulnerability because admin pages render Dataflow profile link variables, tax rate titles, OAuth consumer names, and PayPal certificate filenames without escaping. An administrator…
When was CVE-2026-128040 made public?
CVE-2026-128040 was made public on October 26, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 13, 2026. EchelonGraph's copy of the record carries a last-modified date of November 17, 2026; the record at its source may have been updated since.
Is CVE-2026-128040 actively exploited?
CVE-2026-128040 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-128040?
CVE-2026-128040 has a CVSS base score of 6.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-128040?
A fix for CVE-2026-128040 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-128040 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-128040?

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