How severe is GHSA-7rp6-w7mg-h8rw?

No CVSS score has been assigned to GHSA-7rp6-w7mg-h8rw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7rp6-w7mg-h8rw?

GHSA-7rp6-w7mg-h8rw affects the following packages: org.apache.jena:jena-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-7rp6-w7mg-h8rw?

Update org.apache.jena:jena-core to 4.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7rp6-w7mg-h8rw is resolved across your whole dependency graph.

How do I detect GHSA-7rp6-w7mg-h8rw in my Maven dependencies?

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

How do I mitigate GHSA-7rp6-w7mg-h8rw 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-7rp6-w7mg-h8rw actively exploited in the wild?

No public exploit code has been indexed for GHSA-7rp6-w7mg-h8rw 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-7rp6-w7mg-h8rw?

GHSA-7rp6-w7mg-h8rw has an EPSS (Exploit Prediction Scoring System) score of 4.3%, placing it in the 91th 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-7rp6-w7mg-h8rw?

GHSA-7rp6-w7mg-h8rw 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-7rp6-w7mg-h8rw published, and has it been updated?

GHSA-7rp6-w7mg-h8rw was published on September 20, 2021 and was last updated on December 2, 2024. 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

XML External Entity Reference in Apache JenaGHSA-7rp6-w7mg-h8rw

GHSA-7rp6-w7mg-h8rw is a XML External Entity (XXE) vulnerability in org.apache.jena:jena-core. A fix is available for org.apache.jena:jena-core — see the affected versions and patch details below.

Also known asCVE-2021-39239

Published

Sep 20, 2021

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

4.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.apache.jena:jena-core

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

A vulnerability in XML processing in Apache Jena, in versions up to 4.1.0, may allow an attacker to execute XML External Entities (XXE), including exposing the contents of local files to a remote server.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.jena:jena-core`	all versions	4.2.0`org.apache.jena:jena-core:4.2.0`

Affected Products

1 product · 1 configurations

Application

jenaapache

≤ 4.1.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.jena:jena-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.jena:jena-core to 4.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7rp6-w7mg-h8rw 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-7rp6-w7mg-h8rw in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works