How severe is CVE-2025-52999?

No CVSS score has been assigned to CVE-2025-52999 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-52999?

CVE-2025-52999 affects the following packages: com.fasterxml.jackson.core:jackson-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-52999?

Update com.fasterxml.jackson.core:jackson-core to 2.15.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-52999 is resolved across your whole dependency graph.

How do I detect CVE-2025-52999 in my Maven dependencies?

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

How do I mitigate CVE-2025-52999 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.

How does O3 Security protect against CVE-2025-52999?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-52999 can be triaged on real exposure rather than presence alone.

Is CVE-2025-52999 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-52999 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 CVE-2025-52999?

CVE-2025-52999 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 52th 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-2025-52999?

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

When was CVE-2025-52999 published, and has it been updated?

CVE-2025-52999 was published on June 25, 2025 and was last updated on August 12, 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

CVE-2025-52999 — jackson-core

Fix: FasterXML/jackson-core#943

CVE-2025-52999 is a CWE-121 vulnerability in com.fasterxml.jackson.core:jackson-core. A fix is available for com.fasterxml.jackson.core:jackson-core — see the affected versions and patch details below.

jackson-core Has Potential for StackoverflowError if user parses an input file that contains very deeply nested data

Also known asGHSA-h46c-h94j-95f3

Published

Jun 25, 2025

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-52999.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

☕com.fasterxml.jackson.core:jackson-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

jackson-core contains core low-level incremental ("streaming") parser and generator abstractions used by Jackson Data Processor. In versions prior to 2.15.0, if a user parses an input file and it has deeply nested data, Jackson could end up throwing a StackoverflowError if the depth is particularly large. jackson-core 2.15.0 contains a configurable limit for how deep Jackson will traverse in an input document, defaulting to an allowable depth of 1000. jackson-core will throw a StreamConstraintsException if the limit is reached. jackson-databind also benefits from this change because it uses jackson-core to parse JSON inputs. As a workaround, users should avoid parsing input files from untrusted sources.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.fasterxml.jackson.core:jackson-core`	all versions	2.15.0`com.fasterxml.jackson.core:jackson-core:2.15.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.fasterxml.jackson.core:jackson-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.fasterxml.jackson.core:jackson-core to 2.15.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-52999 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-52999 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-52999. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 HatImportant

Product	Fixed in	Advisory
OCP-Tools-4.12-RHEL-8	`jenkins-0:2.504.2.1750932984-3.el8`	RHSA-2025:10118
OCP-Tools-4.13-RHEL-8	`jenkins-0:2.504.2.1750916374-3.el8`	RHSA-2025:10119
OCP-Tools-4.14-RHEL-8	`jenkins-0:2.504.2.1750903189-3.el8`	RHSA-2025:10120
OCP-Tools-4.15-RHEL-8	`jenkins-0:2.504.2.1750856366-3.el8`	RHSA-2025:10104
OCP-Tools-4.16-RHEL-9	`jenkins-0:2.504.2.1750857144-3.el9`	RHSA-2025:10098
OCP-Tools-4.17-RHEL-9	`jenkins-0:2.504.2.1750851690-3.el9`	RHSA-2025:10097
OCP-Tools-4.18-RHEL-9	`jenkins-0:2.504.2.1750846524-3.el9`	RHSA-2025:10092
Red Hat Enterprise Linux 8	`pki-deps:10.6-8100020250731151637.489197e6`	RHSA-2025:14126

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-52999 in your dependencies?

O3 Security finds CVE-2025-52999 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works