NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

Access Control vulnerability within CoreNLPGHSA-x2p8-rgfm-qw3v

CRITICALFix: stanfordnlp/CoreNLP@5ee097d

GHSA-x2p8-rgfm-qw3v is a critical-severity (CVSS 9.8) CWE-74 vulnerability in edu.stanford.nlp:stanford-corenlp. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for edu.stanford.nlp:stanford-corenlp — see the affected versions and patch details below.

Also known asCVE-2021-44550
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk
0.00%0.60%1.20%1.79%0.5%1.3%May 26Sep 26Nov 26

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
☕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

An Incorrect Access Control vulnerability exists in CoreNLP 4.3.2 via the classifier in NERServlet.java (lines 158 and 159).

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenedu.stanford.nlp:stanford-corenlpall versions4.4.0edu.stanford.nlp:stanford-corenlp:4.4.0

Affected Products

1 product · 1 configurations
Application
corenlpstanford
1 version
4.3.2
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.

An Incorrect Access Control vulnerability exists in CoreNLP 4.3.2 via th…

github.comNVDMar 2022

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. Fix

    Update edu.stanford.nlp:stanford-corenlp to 4.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x2p8-rgfm-qw3v is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

An Incorrect Access Control vulnerability exists in CoreNLP 4.3.2 via the classifier in NERServlet.java (lines 158 and 159).
O3 Security · Impact-Aware SCA

Is GHSA-x2p8-rgfm-qw3v in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Access Control vulnerability within CoreNLP (Critical 9.8)