How severe is CVE-2021-27568?

CVE-2021-27568 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-27568?

CVE-2021-27568 affects the following packages: net.minidev:json-smart (Maven), net.minidev:json-smart (Maven), net.minidev:json-smart-mini (Maven), net.minidev:json-smart (Maven). Ecosystems affected: Maven.

How do I fix CVE-2021-27568?

Update net.minidev:json-smart to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-27568 is resolved across your whole dependency graph.

How do I detect CVE-2021-27568 in my Maven dependencies?

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

How do I mitigate CVE-2021-27568 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 CVE-2021-27568 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2021-27568, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2021-27568?

CVE-2021-27568 has an EPSS (Exploit Prediction Scoring System) score of 2.9%, placing it in the 87th 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 CVE-2021-27568?

CVE-2021-27568 is classified as CWE-754 (CWE-754). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-27568 published, and has it been updated?

CVE-2021-27568 was published on February 23, 2021 and was last updated on October 20, 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

MEDIUM severity

CVE-2021-27568 — json-smart

MEDIUMFix: netplex/json-smart-v2#72

CVE-2021-27568 is a medium-severity (CVSS 5.9) CWE-754 vulnerability in net.minidev:json-smart. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for net.minidev:json-smart — see the affected versions and patch details below.

Improper Check for Unusual or Exceptional Conditions in json-smart

Also known asGHSA-v528-7hrm-frqp

Published

Feb 23, 2021

Updated

Oct 20, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% 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

4 pkgs affected

☕net.minidev:json-smart☕net.minidev:json-smart☕net.minidev:json-smart-mini☕net.minidev:json-smart

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 issue was discovered in netplex json-smart-v1 through 2015-10-23 and json-smart-v2 through 2.4. An exception is thrown from a function, but it is not caught, as demonstrated by NumberFormatException. When it is not caught, it may cause programs using the library to crash or expose sensitive information.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`net.minidev:json-smart`	all versions	1.3.2`net.minidev:json-smart:1.3.2`
☕Maven	`net.minidev:json-smart`	≥ 2.4.0&&< 2.4.1	2.4.1`net.minidev:json-smart:2.4.1`
☕Maven	`net.minidev:json-smart-mini`	all versions	1.3.2`net.minidev:json-smart-mini:1.3.2`
☕Maven	`net.minidev:json-smart`	≥ 2.0.0&&< 2.3.1	2.3.1`net.minidev:json-smart:2.3.1`

Affected Products

7 products · 13 configurations

Application

json-smart-v1json-smart_project

< 1.3.2

range

Application

json-smart-v2json-smart_project

≥ 2.4 && < 2.4.1

range

Application

communications cloud native core policyoracle

1 version

1.14.0

Application

oss support toolsoracle

< 2.12.42

range

Application

peoplesoft enterprise peopletoolsoracle

2 versions

8.588.59

Application

utilities frameworkoracle

3 versions

4.4.0.0.04.4.0.2.04.4.0.3.0

Exploits & PoCs

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

An issue was discovered in netplex json-smart-v1 through 2015-10-23 and …

github.comNVDJul 2021

Report on github.com

github.comNVDJul 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.minidev:json-smart, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update net.minidev:json-smart to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-27568 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 HatModerate

Product	Fixed in	Advisory
Red Hat AMQ Streams 1.8.0	`json-smart`	RHSA-2021:3225
Red Hat Fuse 7.10	`json-smart`	RHSA-2021:5134
Red Hat Fuse 7.9	see advisory	RHSA-2021:3140
Red Hat Integration	see advisory	RHSA-2021:4918
Red Hat Integration Camel Quarkus 2	see advisory	RHSA-2021:4767

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2021-27568 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2021-27568 — json-smart

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2021-27568 in your dependencies?