CVE-2026-61741

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (20th percentile of EPSS-scored CVEs). 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
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

http4s-scala-xml provides EntityDecoder[F, scala.xml.Elem] instances that parse XML message bodies. Prior to versions 0.24.1 and 1.0.0-M39, these decoders used a javax.xml.parsers.SAXParserFactory obtained from SAXParserFactory.newInstance without any security configuration. With the JDK's default settings, the parser resolves DOCTYPE declarations, external general and parameter entities, and external DTDs.An application that uses these decoders to parse untrusted XML is vulnerable to XML External Entity (XXE) attacks. An attacker can craft a request that discloses local files readable by the service process, performs server-side request forgery (SSRF) against internal network resources, and/or causes denial of service through entity expansion. Versions 0.24.1 and 1.0.0-M39 fix the issue.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
57
EG Risk 57/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity93% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 24, 2026

Last Modified

September 30, 2026

Advisory Details (1)

Auto-updated Oct 3, 2026
Patch available. Sources: github.
github Patch Available

XML External Entity (XXE) processing in http4s-scala-xml · Advisory · http4s/http4s-scala-xml · GitHub

https://github.com/http4s/http4s-scala-xml/security/advisories/GHSA-cjx3-73hr-rpw7

Vendor Advisories for CVE-2026-61741(1)

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

Affected Packages

(3 across 1 ecosystem)
Maven(3)
PackageVulnerable rangeFix by version rangeDependents
org.http4s:http4s-scala-xml_2.120.10.0-M10 ... 0.24.0 (240 versions)
  • every version up to 0.24.1: fixed in 0.24.1
—
org.http4s:http4s-scala-xml_2.131.0.0-M10 ... 1.0.0-M9 (33 versions)
  • every version up to 0.24.1: fixed in 0.24.1
  • 1.0.0-M1 up to 1.0.0-M39: fixed in 1.0.0-M39
—
org.http4s:http4s-scala-xml_31.0.0-M22 ... 1.0.0-M38.1 (15 versions)
  • every version up to 0.24.1: fixed in 0.24.1
  • 1.0.0-M1 up to 1.0.0-M39: fixed in 1.0.0-M39
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 23× 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-10-05 01:52 UTCEG score recompute
  2. 2026-10-04 23:22 UTCEPSS rescore
  3. 2026-10-03 14:57 UTCEG score recompute
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-02 19:31 UTCEG score recompute
  6. 2026-10-02 17:56 UTCEPSS rescore
  7. 2026-10-02 00:03 UTCEG score recompute
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:24 UTCEG score recompute
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 16:08 UTCEG score recompute
  12. 2026-09-29 04:32 UTCEG score recompute
  13. 2026-09-29 03:21 UTCEG score recompute
  14. 2026-09-29 00:06 UTCEG score recompute
  15. 2026-09-28 16:22 UTCEG score recompute
  16. 2026-09-28 13:51 UTCEPSS rescore
  17. 2026-09-27 17:10 UTCEG score recompute
  18. 2026-09-26 17:55 UTCEG score recompute
  19. 2026-09-26 15:59 UTCEPSS rescore
  20. 2026-09-26 02:18 UTCEG score recompute
  21. 2026-09-24 18:35 UTCEG score recompute
  22. 2026-09-24 17:57 UTCEG score recompute
  23. 2026-09-24 17:56 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61741?
CVE-2026-61741 is a critical vulnerability published on September 24, 2026. http4s-scala-xml provides EntityDecoder[F, scala.xml.Elem] instances that parse XML message bodies. Prior to versions 0.24.1 and 1.0.0-M39, these decoders used a javax.xml.parsers.SAXParserFactory obtained from SAXParserFactory.newInstance without any security configuration. With the JDK's default…
When was CVE-2026-61741 disclosed?
CVE-2026-61741 was first published on September 24, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61741 actively exploited?
CVE-2026-61741 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61741?
CVE-2026-61741 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61741?
A fix for CVE-2026-61741 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61741 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-61741

Explore →

Is Your Infrastructure Affected by CVE-2026-61741?

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

Book a Demo →Browse All CVEs