CVE-2021-44550: Access Control vulnerability within CoreNLP

Summary

25/02/2022
Yes i
Critical
9.8

CVE-2021-44550: Access Control vulnerability within CoreNLP. Affects edu.stanford.nlp:stanford-corenlp versions < 4.4.0. Fixed in 4.4.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

CoreNLP is a Java library that provides a set of natural language processing tools. It is commonly used for tasks such as tokenization, part-of-speech tagging, named entity recognition, and sentiment analysis. The vulnerability affects CoreNLP version 4.3.2 and earlier.

Vulnerability Detail

An Incorrect Access Control vulnerability exists in CoreNLP 4.3.2 via the classifier in NERServlet.java (lines 158 and 159). This vulnerability allows an attacker to bypass access controls and potentially gain unauthorized access to sensitive information or perform malicious actions. The severity of this vulnerability is rated as CRITICAL with a CVSS score of 9.8. It is classified under CWE-863.

How To Fix

Latest published version: 4.6.0 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

4.4.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update to the fixed version as soon as possible.

Conclusion

The Access Control vulnerability in CoreNLP 4.3.2 and earlier can lead to unauthorized access and potential misuse of sensitive information. It is crucial to update to CoreNLP version 4.4.0 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for edu.stanford.nlp:stanford-corenlp →

Share this vulnerability

FAQ

CoreNLP is a Java library for natural language processing tasks.

This vulnerability allows unauthorized access to sensitive information or malicious actions.

The severity of this vulnerability is rated as CRITICAL with a CVSS score of 9.8.

Upgrade to CoreNLP version 4.4.0 or later.

No, it is necessary to update to the fixed version.

Related vulnerabilities

Recent vulnerabilities recorded for edu.stanford.nlp:stanford-corenlp.

How To Fix

Latest published version: 4.6.0 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

4.4.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback