Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-wf8f-6423-gfxg

Jackson-core Vulnerable to Memory Disclosure via Source Snippet in JsonLocation

CVSS 4.0 MediumEPSS 0.0041 · 35th percentile

Published by the GitHub Advisory Database at 7 Jun 2025, 00:10 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
com.fasterxml.jackson.core:jackson-coreMaven>=2.0.0, <2.13.02.13.0
Identifiers
GHSA-wf8f-6423-gfxg · CVE-2025-49128
Weakness (CWE)
CWE-209
Tags
Published
7 Jun 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Jackson-core versions 2.0.0 up to but not including 2.13.0 are affected. When parsing JSON from a byte array with an offset, exception messages can include up to 500 bytes of unrelated memory from the start of the array, which may expose residual data in pooled or reused buffers if the message is returned to clients. Users should upgrade to jackson-core 2.13.0 or later; as a workaround, avoid returning parser exception messages to clients or disable source inclusion in exceptions.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.0 Medium 3.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0041, the 35th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 6 Jun 2025, 20:47 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:17 UTC First seen by agentprime
  3. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.