CVE-2026-114128

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

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

Score 6.5 from GitHub Security Advisory (severity: MODERATE) published 2026-10-22. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-107411 (ENISA EUVD) · GHSA-98hj-9722-w3j8 (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
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.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Astro is a web framework for content-driven websites. Prior to 7.3.2, Astro's JSX and MDX rendering pipeline treats string children of script and style elements as trusted HTML without distinguishing compiler-generated literal content from dynamic expression values. An application that passes attacker-controlled data directly as a dynamic child can allow a value containing a closing script or style tag to terminate the element and inject arbitrary HTML and JavaScript. Other JSX expression contexts escape dynamic strings automatically; the issue is limited to script and style children rendered through the astro:jsx renderer, including MDX components. Successful exploitation can produce reflected or stored cross-site scripting under the application's origin. This issue is fixed in 7.3.2.

CVSS v3
6.5
EG Score
6.5MEDIUMhigh confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 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 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.3%
EPSS %ILE
25th
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.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 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-10-31). 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 21, 2026

Last Modified

October 23, 2026

Advisory Details (4)

Auto-updated Oct 22, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

XSS via unescaped dynamic content in JSX and MDX script or style elements · Advisory · withastro/astro · GitHub

https://github.com/withastro/astro/security/advisories/GHSA-98hj-9722-w3j8
GitHub release Patch Available

astro@7.3.2

Patch available: withastro/astro astro@7.3.2

https://github.com/withastro/astro/releases/tag/astro@7.3.2
GitHub pull request Patch Available

Only treat literal script/style content as raw in MDX rendering

Patch available: withastro/astro create-astro@5.3.0 (PR #17896 merged 2026-09-08)

https://github.com/withastro/astro/pull/17896
GitHub commit Patch Available

commit a548223607b9 (withastro/astro)

Patch available: withastro/astro create-astro@5.3.0 (contains commit a548223607b9)

https://github.com/withastro/astro/commit/a548223607b9bb146d5d90ddda495343f9a2a739

Vendor Advisories for CVE-2026-114128(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmastro @ 7.3.2 (fixes < 7.3.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
astro—
  • every version up to 7.3.2: fixed in 7.3.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 20× 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-01 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  2. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-98hj-9722-w3j8 · GitHub severity MODERATE · GitHub CVSS 6.5
  3. 2026-11-01 07:59 UTCEG score recompute
  4. 2026-10-31 21:25 UTCOSV refresh
  5. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-10-25 14:50 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  15. 2026-10-23 15:18 UTCEG score recompute
  16. 2026-10-22 17:31 UTCEG score recompute
  17. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  18. 2026-10-21 18:26 UTCEG score recompute
  19. 2026-10-21 17:46 UTCEG score recomputeFirst assessed: 6.5 MEDIUM
  20. 2026-10-21 17:45 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-114128?
CVE-2026-114128 is a medium-severity vulnerability; its CVE record was published on October 21, 2026. Astro is a web framework for content-driven websites. Prior to 7.3.2, Astro's JSX and MDX rendering pipeline treats string children of script and style elements as trusted HTML without distinguishing compiler-generated literal content from dynamic expression values. An application that passes…
When was the CVE record for CVE-2026-114128 published?
The CVE record for CVE-2026-114128 was published on October 21, 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 October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-114128 actively exploited?
CVE-2026-114128 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-114128?
CVE-2026-114128 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-114128?
A fix for CVE-2026-114128 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-114128 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-114128

Explore →

Is Your Infrastructure Affected by CVE-2026-114128?

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

Book a Demo →Browse All CVEs