How severe is GHSA-6fhj-vr9j-g45r?

GHSA-6fhj-vr9j-g45r has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6fhj-vr9j-g45r?

GHSA-6fhj-vr9j-g45r affects the following packages: org.cyclonedx:cyclonedx-core-java (Maven). Ecosystems affected: Maven.

How do I fix GHSA-6fhj-vr9j-g45r?

Update org.cyclonedx:cyclonedx-core-java to 11.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6fhj-vr9j-g45r is resolved across your whole dependency graph.

How do I detect GHSA-6fhj-vr9j-g45r in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.cyclonedx:cyclonedx-core-java, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6fhj-vr9j-g45r if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-6fhj-vr9j-g45r actively exploited in the wild?

No public exploit code has been indexed for GHSA-6fhj-vr9j-g45r yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6fhj-vr9j-g45r?

GHSA-6fhj-vr9j-g45r has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 34th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6fhj-vr9j-g45r?

GHSA-6fhj-vr9j-g45r is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6fhj-vr9j-g45r published, and has it been updated?

GHSA-6fhj-vr9j-g45r was published on November 10, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CycloneDX Core (Java): BOM validation is vulnerable to XML External Entity injectionGHSA-6fhj-vr9j-g45r

HIGHFix: CycloneDX/cyclonedx-core-java#737

GHSA-6fhj-vr9j-g45r is a high-severity (CVSS 7.5) XML External Entity (XXE) vulnerability in org.cyclonedx:cyclonedx-core-java. A fix is available for org.cyclonedx:cyclonedx-core-java — see the affected versions and patch details below.

Also known asCVE-2025-64518

Published

Nov 10, 2025

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6fhj-vr9j-g45r.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk-0.00%

Lower risk than most CVEs34th percentile — riskier than 34% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.cyclonedx:cyclonedx-core-java

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The XML Validator used by cyclonedx-core-java was not configured securely, making the library vulnerable to XML External Entity (XXE) injection.

The fix for GHSA-683x-4444-jxh8 / CVE-2024-38374 has been incomplete in that it only fixed parsing of XML BOMs, but not validation.

Patches

The vulnerability has been fixed in cyclonedx-core-java version 11.0.1.

Workarounds

If feasible, applications can reject XML documents before handing them to cyclonedx-core-java for validation. This may be an option if incoming CycloneDX BOMs are known to be in JSON format.

References

The issue was introduced via https://github.com/CycloneDX/cyclonedx-core-java/commit/162aa594f347b3f612fe0a45071693c3cd398ce9
The issue was fixed via https://github.com/CycloneDX/cyclonedx-core-java/pull/737
https://cheatsheetseries.owasp.org/cheatsheets/XML_External_Entity_Prevention_Cheat_Sheet.html#schemafactory

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.cyclonedx:cyclonedx-core-java`	≥ 2.1.0&&< 11.0.1	11.0.1`org.cyclonedx:cyclonedx-core-java:11.0.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.cyclonedx:cyclonedx-core-java, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.cyclonedx:cyclonedx-core-java to 11.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6fhj-vr9j-g45r is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

The flaw has been rated High severity, because a remote attacker could craft a malicious CycloneDX SBOM that, when validated by an affected system, may result in disclosure of sensitive information from local files or internal network resources. Exploitation does not require authentication or user interaction, but it…

Workaround published by Red Hat

Reject or block XML-formatted BOMs from untrusted sources before handing them to the library (e.g., require BOMs to be JSON or only accept BOMs from trusted origins).

Source: Red Hat security advisory for GHSA-6fhj-vr9j-g45r (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat build of Quarkus 3.20.4.redhat	`org.cyclonedx/cyclonedx-core-java:11.0.1.redhat-00001`	RHSA-2025:22195
Red Hat build of Quarkus 3.27.1.redhat	`org.cyclonedx/cyclonedx-core-java:11.0.1.redhat-00001`	RHSA-2025:22622

Frequently Asked Questions

### Impact The XML [`Validator`](https://docs.oracle.com/javase/8/docs/api/javax/xml/validation/Validator.html) used by cyclonedx-core-java was not configured securely, making the library vulnerable to XML External Entity (XXE) injection. The fix for GHSA-683x-4444-jxh8 / CVE-2024-38374 has been incomplete in that it only fixed *parsing* of XML BOMs, but not *validation*. ### Patches The vulnerability has been fixed in cyclonedx-core-java version 11.0.1. ### Workarounds If feasible, applications can reject XML documents before handing them to cyclonedx-core-java for validation. This may