Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61741 critical CVSS 9.3

XXE (XML External Entity) in org.http4s:http4s-scala-xml_2.12 (CVE-2026-61741)

Summary

Vulnerability in org.http4s:http4s-scala-xml_2.12 (CVE-2026-61741). Confidential information can be exposed externally. Exploitable via javax.xml.parsers.SAXParserFactory. Mitigation: upgrade to 0.24.1 or later.

Original description

The description as published by the source.

http4s-scala-xml provides EntityDecoder[F, scala.xml.Elem] instances that parse XML message bodies. 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.

Impact

Any service that derives an XML EntityDecoder from this library and parses attacker-controlled input is affected.

Patches

The default SAXParserFactory is now hardened:

  • secure processing is enabled
  • DOCTYPE declarations are disallowed
  • external general/parameter entities and external DTD loading are disabled
  • DTD URIs are not resolved
  • XInclude is disabled.

These defaults match scala.xml.XMLLoader's defaults since 2.0.0.

Workarounds

Before upgrading, override ElemInstances#saxFactory with a hardened factory.

  val secured = new ElemInstances {
    override protected val saxFactory = {
      val f = javax.xml.parsers.SAXParserFactory.newInstance
      f.setFeature("http://apache.org/xml/features/disallow-doct…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-61741 has been found in org.http4s:http4s-scala-xml_2.12.
Attackers can target a specific entry point like javax.xml.parsers.SAXParserFactory over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.3/10.
What to do: upgrade org.http4s:http4s-scala-xml_2.12 to 0.24.1 or later.
If unsure, ask your IT team or search "org.http4s:http4s-scala-xml_2.12 CVE-2026-61741" on the vendor's site.

CVE-2026-61741 (org.http4s:http4s-scala-xml_2.12) — CWE-611 / CVSS v3 9.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: javax.xml.parsers.SAXParserFactory / SAXParserFactory.newInstance / EntityDecoder / DOCTYPE
Patched: 0.24.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-611) exists in org.http4s:http4s-scala-xml_2.12. Attackers reach the vulnerable code path via javax.xml.parsers.SAXParserFactory without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of org.http4s:http4s-scala-xml_2.12. Attack surface: javax.xml.parsers.SAXParserFactory / SAXParserFactory.newInstance / EntityDecoder / DOCTYPE.

🔥 Severity

Severity: Critical (CVSS 9.3/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.24.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.http4s:http4s-scala-xml_2.12 を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.http4s:http4s-scala-xml_2.12 to 0.24.1

    ステージング環境で 0.24.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.http4s:http4s-scala-xml_2.12
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.24.1"}]}]
maven org.http4s:http4s-scala-xml_2.13
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.0-M39"}]}]
maven org.http4s:http4s-scala-xml_3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.0-M39"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details