Skip to main content
CVE-2025-49128VulnerabilityPublished Updated

CVE-2025-49128: FasterXML jackson-core · Generation of Error Message Containing Sensitive Information

Affects FasterXML jackson-coreSource CVE Database V5

0

Not known to be exploited · CVSS 4.0 Medium · fixed in 2.13.0 : update FasterXML jackson-core when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
4.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.13.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Mavencom.fasterxml.jackson.core/jackson-corepkg:maven/com.fasterxml.jackson.core/jackson-coreOther threatsAffected–Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available by upgrading jackson-core to version 2.13.0 or later. If upgrading is not immediately feasible, applications should mitigate by disabling the exposure of exception messages to clients and/or disabling source inclusion in exceptions to prevent embedding source content in error messages, thereby avoiding information leakage.

Description

A vulnerability in jackson-core versions from 2.0.0 up to but not including 2.13.0 allows unintended memory content to be included in exception messages. This occurs due to improper handling in the JsonLocation. _appendSourceDesc method when parsing JSON from byte arrays with offsets, potentially exposing sensitive information from pooled or reused buffers. The issue was fixed in version 2.13.0.

References

Community reviews

Loading reviews…