# CVE-2026-61741: http4s-scala-xml has an XML External Entity (XXE) processing issue > Attackers can exploit unconfigured XML parsers in http4s-scala-xml to read local files, perform SSRF, or cause denial of service. - **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 24 Sep 2026 - **Updated:** 29 Sep 2026 - **Also known as:** GHSA-cjx3-73hr-rpw7 ## What is CVE-2026-61741? CVE-2026-61741 is a critical vulnerability in http4s-scala-xml, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-611 (Improper Restriction of XML External Entity Reference) ## Which versions are affected by CVE-2026-61741? 10 open source packages ship an affected version, including org.http4s:http4s-scala-xml_2.13, org.http4s:http4s-scala-xml_2.12 and org.http4s:http4s-scala-xml_3. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.http4s:http4s-scala-xml_2.13` | Maven | All versions | 0.24.1 | | `org.http4s:http4s-scala-xml_2.13` | Maven | All versions | 0.24.1 | | `org.http4s:http4s-scala-xml_2.13` | Maven | From 1.0.0-M1 | 1.0.0-M39 | | `org.http4s:http4s-scala-xml_2.13` | Maven | From 1.0.0-M1 | 1.0.0-M39 | | `org.http4s:http4s-scala-xml_2.12` | Maven | All versions | 0.24.1 | | `org.http4s:http4s-scala-xml_2.12` | Maven | All versions | 0.24.1 | | `org.http4s:http4s-scala-xml_3` | Maven | All versions | 0.24.1 | | `org.http4s:http4s-scala-xml_3` | Maven | All versions | 0.24.1 | | `org.http4s:http4s-scala-xml_3` | Maven | From 1.0.0-M1 | 1.0.0-M39 | | `org.http4s:http4s-scala-xml_3` | Maven | From 1.0.0-M1 | 1.0.0-M39 | ## How do I fix CVE-2026-61741? Upgrade org.http4s:http4s-scala-xml_2.13 to a fixed version for your release line: 0.24.1 or 1.0.0-M39. ## Is CVE-2026-61741 being exploited? There is no known exploitation of CVE-2026-61741 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-61741 and fix it if it is affected. What it is: CVE-2026-61741 is a critical vulnerability in http4s-scala-xml, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-61741 in the wild and no public exploit code. Affected packages and fixed versions: - org.http4s:http4s-scala-xml_2.13 (Maven): affected all versions; fixed in 0.24.1 - org.http4s:http4s-scala-xml_2.13 (Maven): affected all versions; fixed in 0.24.1 - org.http4s:http4s-scala-xml_2.13 (Maven): affected from 1.0.0-M1; fixed in 1.0.0-M39 - org.http4s:http4s-scala-xml_2.13 (Maven): affected from 1.0.0-M1; fixed in 1.0.0-M39 - org.http4s:http4s-scala-xml_2.12 (Maven): affected all versions; fixed in 0.24.1 - org.http4s:http4s-scala-xml_2.12 (Maven): affected all versions; fixed in 0.24.1 - org.http4s:http4s-scala-xml_3 (Maven): affected all versions; fixed in 0.24.1 - org.http4s:http4s-scala-xml_3 (Maven): affected all versions; fixed in 0.24.1 - org.http4s:http4s-scala-xml_3 (Maven): affected from 1.0.0-M1; fixed in 1.0.0-M39 - org.http4s:http4s-scala-xml_3 (Maven): affected from 1.0.0-M1; fixed in 1.0.0-M39 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-61741/ (Markdown: https://insights.sbomify.com/CVE-2026-61741/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61741 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61741 - OSV: https://osv.dev/vulnerability/CVE-2026-61741 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-61741/ Summaries are generated and may contain mistakes; the official description above is the record.