Read the docs

XML external entity flaw in Eclipse AAS4J lets attackers read files

Priority LOW 34Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
None · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Eclipse AAS4J before 3.0.1 validates untrusted XML with a default JAXP Validator that resolves external DTDs and external entities in XmlSchemaValidator.validateSchema(). An attacker who supplies a crafted AAS XML document or AASX package can read local files from the host and send their contents to an attacker-controlled server. The validating process can also make arbitrary outbound requests (SSRF). Validation still returns no errors.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

In Eclipse AAS4J before 3.0.1, `XmlSchemaValidator.validateSchema()` (and `AASXValidator.validateSchema()`, which calls it) validates untrusted XML with a default JAXP `Validator` that resolves external DTDs and external entities. An attacker who supplies a crafted AAS XML document or AASX package can read local files from the host, send their contents out-of-band to an attacker-controlled server, and make the validating process send arbitrary outbound requests (SSRF). Validation still returns no errors. Details: - Vulnerable code: `dataformat-xml/src/main/java/org/eclipse/digitaltwin/aas4j/v3/dataformat/xml/XmlSchemaValidator.java`. `schema.newValidator().validate(new StreamSource(...))` runs without `ACCESS_EXTERNAL_DTD` / `ACCESS_EXTERNAL_SCHEMA` restrictions and without `disallow-doctype-decl`. - Second entry point: `dataformat-aasx/src/main/java/org/eclipse/digitaltwin/aas4j/v3/dataformat/aasx/AASXValidator.java`. The AAS XML part of an `.aasx` package is passed unchanged to the vulnerable validator. - `XmlDeserializer` (Jackson/Woodstox) is not affected, because DTD support is disabled by default there. - Present since the initial import of the code base (commit `cc9da52`). - Fix: harden the validator by setting `ACCESS_EXTERNAL_DTD` and `ACCESS_EXTERNAL_SCHEMA` to `""` and rejecting `DOCTYPE` declarations. The bundled `AAS.xsd` does not need DTDs, so no functionality is lost.

Why it matters now

EPSS 0.00371 31st percentileScored 2026-11-16
Fix Fixed Eclipse AAS Model for Java (Eclipse AAS4J) (Eclipse Foundation): 3.0.1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
Eclipse FoundationEclipse AAS Model for Java (Eclipse AAS4J)before 3.0.13.0.1Patch availableCNA
  • Eclipse AAS Model for Java (Eclipse AAS4J) VendorEclipse Foundation Affected before 3.0.1 Fixed in 3.0.1 Patch available CNA

Remediation

Upgrade Eclipse AAS4J to version 3.0.1 or later, which fixes this flaw. The fix sets ACCESS_EXTERNAL_DTD and ACCESS_EXTERNAL_SCHEMA to empty strings and rejects DOCTYPE declarations.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA Eclipse AAS Model for Java (Eclipse AAS4J) (Eclipse Foundation) Fixed in 3.0.1

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-127031
  2. 2026-11-13 Alias added: GHSA-5jff-rm7x-vvwf

References

  • TI-2023-23979 HTTP/2 request cancellation lets attackers exhaust server resources KEVCVSS 3.1HIGH 7.5
  • TI-2026-81947 Unauthenticated command injection in Eclipse Che che-machine-exec CVSS 3.1CRITICAL 9.8
  • TI-2026-13216 CWE-863: ABAC authorization bypass via trailing slash route normalization in Eclipse BaSyx Go Components CVSS 3.1CRITICAL 9.8
  • TI-2026-06514 Path traversal in Eclipse BaSyx CVSS 3.1CRITICAL 10.0
  • TI-2026-01382 In the Eclipse Theia Website repository, the GitHub Actions workflow… CVSS 3.1CRITICAL 10.0
  • TI-2026-74697 Authentication bypass in Eclipse Jetty EthereumAuthenticator CVSS 4.0CRITICAL 9.3
See all 482 →

Sources