CVE-2026-127031VulnerabilityPublished 13 Nov 2026

In Eclipse AAS4J before 3.0.1, XmlSchemaValidator.validateSchema() (and AASXValidator.validateSchema(), which calls

Source GCVE Database

Compare

Authoritative record:CVE-2026-127031· High 7.7

Not known to be exploited · CVSS 7.7 High : upgrade to 3.0.1 soon.

Data as of 13 Nov 2026, 16:23 UTC

CVSS 4.0 base score

7.7High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (eclipse)	CVSS 4.0	7.7

Patch: Available – fixed in 3.0.1

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: High
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: High: There is a total loss of confidentiality, resulting in all resources within the Subsequent System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-5jff-rm7x-vvwf

What to do

Upgrade Eclipse AAS Model for Java (Eclipse AAS4J) and org.eclipse.digitaltwin/aas4j to 3.0.1.

Affected software

Product	Affected	Fixed in
Eclipse FoundationEclipse AAS Model for Java (Eclipse AAS4J)	Affected <3.0.1	Fixed in 3.0.1
Mavenorg.eclipse.digitaltwin/aas4j`pkg:maven/org.eclipse.digitaltwin/aas4j`Other threats	Affected <3.0.1	Fixed in 3.0.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Eclipse AAS4J version 3.0.1 or later, where the vulnerability is fixed by disabling external DTD and schema access and rejecting DOCTYPE declarations in the XML validator. If upgrading is not immediately possible, consider applying equivalent configuration changes to the XML validator to set ACCESS_EXTERNAL_DTD and ACCESS_EXTERNAL_SCHEMA to empty strings and disallow DOCTYPE declarations to prevent external entity resolution. Note that the bundled AAS.xsd schema does not require DTDs, so these restrictions will not impact normal functionality.

Description

Eclipse AAS4J versions before 3.0.1 contain a vulnerability in the XmlSchemaValidator.validateSchema() method, which uses a default JAXP Validator that allows resolution of external DTDs and entities. This enables an attacker supplying a crafted AAS XML document or AASX package to read local files on the host and exfiltrate their contents, as well as perform server-side request forgery (SSRF) by making the validator send arbitrary outbound requests. The validation process does not report errors despite the malicious activity. The vulnerability is fixed in version 3.0.1 by disabling external DTD and schema access and rejecting DOCTYPE declarations.

Impact

An attacker can exploit this vulnerability by supplying a crafted AAS XML document or AASX package to the vulnerable validator, enabling them to read arbitrary local files on the host system and exfiltrate their contents to an attacker-controlled server. The attacker can also induce the validator to send arbitrary outbound network requests, resulting in server-side request forgery (SSRF). The validation process does not detect or report these malicious activities, allowing stealthy exploitation. This can lead to unauthorized disclosure of sensitive information and potential network abuse.

References

Community reviews

Loading reviews…