Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

XML External Entity Reference in edu.stanford.nlp:stanford-corenlpGHSA-mh83-jcw5-rjh8

MEDIUMFix: stanfordnlp/corenlp@1f52136

GHSA-mh83-jcw5-rjh8 is a medium-severity (CVSS 6.1) XML External Entity (XXE) vulnerability in edu.stanford.nlp:stanford-corenlp. 1 public exploit reference exists, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Also known asCVE-2022-0198
Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
1 known
Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk
0.00%0.41%0.83%1.24%0.2%0.7%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-mh83-jcw5-rjh8 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
☕edu.stanford.nlp:stanford-corenlp

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

The TransformXML() function makes use of SAXParser generated from a SAXParserFactory with no FEATURE_SECURE_PROCESSING set, allowing for XXE attacks.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
☕Mavenedu.stanford.nlp:stanford-corenlpall versionsNo fix

Affected Products

1 product · 1 configurations
Application
corenlpstanford
≤ 4.3.2
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Remediation status

    No patched version of edu.stanford.nlp:stanford-corenlp has shipped for GHSA-mh83-jcw5-rjh8 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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

The TransformXML() function makes use of SAXParser generated from a SAXParserFactory with no FEATURE_SECURE_PROCESSING set, allowing for XXE attacks.
O3 Security · Impact-Aware SCA

Is GHSA-mh83-jcw5-rjh8 in your dependencies?

Find it across Maven, including transitive dependencies.

XML External Entity Reference in edu.stanford.nlp:stanford…