BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-49128High confidence

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

FasterXML · jackson-core

Official source article: GitHub GHSA-WF8F-6423-GFXG ↗. Check the applicable product and release in the original source.

4.0MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 168 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 0.39% for the current model date.

Compensating controls

  • Apply the linked authoritative mitigation while planning the permanent fix.
  • Restrict local access and enforce least privilege on affected hosts.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs FasterXML jackson-core and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 168 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcejackson-coreVendor fix publishedDebian records a fixed source-package version for this release.2.13.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcejackson-coreVendor fix publishedDebian records a fixed source-package version for this release.2.13.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcejackson-coreVendor fix publishedDebian records a fixed source-package version for this release.2.13.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcejackson-coreVendor fix publishedDebian records a fixed source-package version for this release.2.13.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavencom.fasterxml.jackson.core:jackson-coreECOSYSTEM: introduced 2.0.0; fixed 2.13.02.13.0OSV record ↗aggregator derived · 10 Sep 2026
mavencom.fasterxml.jackson.core:jackson-core>= 2.0.0, < 2.13.02.13.0GitHub advisory ↗upstream repository advisory · 7 Jun 2025
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-49128 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitycom.fasterxml.jackson.core/jackson-core: Jackson-core Memory Disclosure via Source Snippet in JsonLocation
168 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • jackson-core as a component of Cryostat 4
  • jackson-core as a component of Logging Subsystem for Red Hat OpenShift
  • jenkins-2-plugins.src as a component of OpenShift Developer Tools and Services
  • jenkins.src as a component of OpenShift Developer Tools and Services
  • openshift-serverless-1/kn-ekb-dispatcher-rhel8 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-ekb-kafka-controller-rhel8 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-ekb-post-install-rhel8 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-ekb-receiver-rhel8 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-ekb-webhook-kafka-rhel8 as a component of OpenShift Serverless
  • openshift-serverless-1/kn-eventing-istio-controller-rhel8 as a component of OpenShift Serverless
  • jackson-core as a component of Red Hat Ansible Automation Platform 2
  • python-drools-jpy-jar.src as a component of Red Hat Ansible Automation Platform 2
Summary
A flaw was found in the Jackson-core `JsonLocation._appendSourceDesc` method. This vulnerability allows up to 500 bytes of unintended memory content to be included in exception messages. This issue may lead to unintended information disclosure.
Remediation
If upgrading is not immediately possible, applications can mitigate the issue by disabling exception message exposure to clients to avoid returning parsing exception messages in HTTP responses and/or disabling source inclusion in exceptions to prevent Jackson from embedding any source content in exception messages, avoiding leakage.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-17366

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 168 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Jackson-core contains core low-level incremental ("streaming") parser and generator abstractions used by Jackson Data Processor. Starting in version 2.0.0 and prior to version 2.13.0, a flaw in jackson-core's `JsonLocation._appendSourceDesc` method allows up to 500 bytes of unintended memory content to be included in exception messages. When parsing JSON from a byte array with an offset and length, the exception message incorrectly reads from the beginning of the array instead of the logical payload start. This results in possible information disclosure in systems using pooled or reused buffers, like Netty or Vert.x. This issue was silently fixed in jackson-core version 2.13.0, released on September 30, 2021, via PR #652. All users should upgrade to version 2.13.0 or later. If upgrading is not immediately possible, applications can mitigate the issue by disabling exception message exposure to clients to avoid returning parsing exception messages in HTTP responses and/or disabling source inclusion in exceptions to prevent Jackson from embedding any source content in exception messages, avoiding leakage.

What

Jackson-core contains core low-level incremental ("streaming") parser and generator abstractions used by Jackson Data Processor. Starting in version 2.0.0 and prior to version 2.13.0, a flaw in jackson-core's `JsonLocation._appendSourceDesc` method allows up to 500 bytes of unintended memory content to be included in exception messages. When parsing JSON from a byte array with an offset and length, the exception message incorrectly reads from the beginning of the array instead of the logical payload start. This results in possible information disclosure in systems using pooled or reused buffers, like Netty or Vert.x. This issue was silently fixed in jackson-core version 2.13.0, released on September 30, 2021, via PR #652. All users should upgrade to version 2.13.0 or later. If upgrading is not immediately possible, applications can mitigate the issue by disabling exception message exposure to clients to avoid returning parsing exception messages in HTTP responses and/or disabling source inclusion in exceptions to prevent Jackson from embedding any source content in exception messages, avoiding leakage.

Why

The product generates an error message that includes sensitive information about its environment, users, or associated data.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

What

Jackson-core contains core low-level incremental ("streaming") parser and generator abstractions used by Jackson Data Processor. Starting in version 2.0.0 and prior to version 2.13.0, a flaw in jackson-core's `JsonLocation._appendSourceDesc` method allows up to 500 bytes of unintended memory content to be included in exception messages. When parsing JSON from a byte array with an offset and length, the exception message incorrectly reads from the beginning of the array instead of the logical payload start. This results in possible information disclosure in systems using pooled or reused buffers, like Netty or Vert.x. This issue was silently fixed in jackson-core version 2.13.0, released on September 30, 2021, via PR #652. All users should upgrade to version 2.13.0 or later. If upgrading is not immediately possible, applications can mitigate the issue by disabling exception message exposure to clients to avoid returning parsing exception messages in HTTP responses and/or disabling source inclusion in exceptions to prevent Jackson from embedding any source content in exception messages, avoiding leakage.

Why

The product generates an error message that includes sensitive information about its environment, users, or associated data.

How

An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.

Likely attack path
local access → Generation of Error Message Containing Sensitive Information → obtain information outside the intended access boundary
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-209 ↗

CWE-209: Generation of Error Message Containing Sensitive Information. The product generates an error message that includes sensitive information about its environment, users, or associated data.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
UnauthenticatedCWE-209Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-2355Oracle Enterprise Manager: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Oracle Enterprise Manager ausnutzen, um die Vertraulichkeit und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2025-1262FasterXML Jackson: Schwachstelle ermöglicht Offenlegung von Informationen

Ein lokaler Angreifer kann eine Schwachstelle in FasterXML Jackson ausnutzen, um Informationen offenzulegen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0556Multiples vulnérabilités dans les produits VMware

VERecord?id=CVE-2025-4330 Référence CVE CVE-2025-4435 https://www.cve.org/CVERecord?id=CVE-2025-4435 Référence CVE CVE-2025-4516 https://www.cve.org/CVERecord?id=CVE-2025-4516 Référence CVE CVE-2025-4517 https://www.cve.org/CVERecord?id=CVE-2025-4517 Référence CVE CVE-2025-46392 https://www.cve.org/CVERecord?id=CVE-2025-46392 Référence CVE CVE-2025-47914 https://www.cve.org/CVERecord?id=CVE-2025-47914 Référence CVE CVE-2025-48734 https://www.cve.org/CVERecord?id=CVE-2025-48734 Référence CVE CVE-2025-48924 https://www.cve.org/CVERecord?id=CVE-2025-48924 Référence CVE CVE-2025-48976 https://www.cve.org/CVERecord?id=CVE-2025-48976 Référence CVE CVE-2025-49128 https://www.cve.org/CVERecord?id=CVE-2025-49128 Référence CVE CVE-2025-50077 https://www.cve.org/CVERecord?id=CVE-2025-50077 Référence CVE CVE-2025-50078 https://www.cve.org/CVERecord?id=CVE-2025-50078 Référence CVE CVE-2025-50079 https://www.cve.org/CVERecord?id=CVE-2025-50079 Référence CVE CVE-2025-50080 https://www.cve.org/CVERecord?id=CVE-2025-50080 Référence CVE CVE-2025-50082 https://www.cve.org/CVERecord?id=CVE-2025-50082 Référence CVE CVE-2025-50083 https://www.cve.org/CVERecord?id=CVE-2025-50083 Référence CVE CVE-2025-50084 https://www.cve.org/CVERecord?id=CVE-2025-50084 Référence CVE CVE-2025-50085 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0500Multiples vulnérabilités dans VMware Tanzu

d?id=CVE-2025-25193 Référence CVE CVE-2025-26791 https://www.cve.org/CVERecord?id=CVE-2025-26791 Référence CVE CVE-2025-27555 https://www.cve.org/CVERecord?id=CVE-2025-27555 Référence CVE CVE-2025-27789 https://www.cve.org/CVERecord?id=CVE-2025-27789 Référence CVE CVE-2025-27821 https://www.cve.org/CVERecord?id=CVE-2025-27821 Référence CVE CVE-2025-33042 https://www.cve.org/CVERecord?id=CVE-2025-33042 Référence CVE CVE-2025-41249 https://www.cve.org/CVERecord?id=CVE-2025-41249 Référence CVE CVE-2025-48734 https://www.cve.org/CVERecord?id=CVE-2025-48734 Référence CVE CVE-2025-48924 https://www.cve.org/CVERecord?id=CVE-2025-48924 Référence CVE CVE-2025-49128 https://www.cve.org/CVERecord?id=CVE-2025-49128 Référence CVE CVE-2025-52999 https://www.cve.org/CVERecord?id=CVE-2025-52999 Référence CVE CVE-2025-54550 https://www.cve.org/CVERecord?id=CVE-2025-54550 Référence CVE CVE-2025-54920 https://www.cve.org/CVERecord?id=CVE-2025-54920 Référence CVE CVE-2025-55163 https://www.cve.org/CVERecord?id=CVE-2025-55163 Référence CVE CVE-2025-56200 https://www.cve.org/CVERecord?id=CVE-2025-56200 Référence CVE CVE-2025-58056 https://www.cve.org/CVERecord?id=CVE-2025-58056 Référence CVE CVE-2025-58057 https://www.cve.org/CVERecord?id=CVE-2025-58057 Référence CVE CVE-2025-5889 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0249Multiples vulnérabilités dans les produits IBM

rd?id=CVE-2025-4673 Référence CVE CVE-2025-47906 https://www.cve.org/CVERecord?id=CVE-2025-47906 Référence CVE CVE-2025-47912 https://www.cve.org/CVERecord?id=CVE-2025-47912 Référence CVE CVE-2025-47913 https://www.cve.org/CVERecord?id=CVE-2025-47913 Référence CVE CVE-2025-47935 https://www.cve.org/CVERecord?id=CVE-2025-47935 Référence CVE CVE-2025-47944 https://www.cve.org/CVERecord?id=CVE-2025-47944 Référence CVE CVE-2025-48068 https://www.cve.org/CVERecord?id=CVE-2025-48068 Référence CVE CVE-2025-48387 https://www.cve.org/CVERecord?id=CVE-2025-48387 Référence CVE CVE-2025-48997 https://www.cve.org/CVERecord?id=CVE-2025-48997 Référence CVE CVE-2025-49128 https://www.cve.org/CVERecord?id=CVE-2025-49128 Référence CVE CVE-2025-50106 https://www.cve.org/CVERecord?id=CVE-2025-50106 Référence CVE CVE-2025-50537 https://www.cve.org/CVERecord?id=CVE-2025-50537 Référence CVE CVE-2025-5187 https://www.cve.org/CVERecord?id=CVE-2025-5187 Référence CVE CVE-2025-5222 https://www.cve.org/CVERecord?id=CVE-2025-5222 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
NCSC-NL · Dutch · NCSC-2025-0332Kwetsbaarheden verholpen in Oracle Enterprise Manager

Recent vulnerabilities in Jackson-core and Oracle Enterprise Manager expose systems to information disclosure and unauthorized data access, with fixes available for Jackson-core in version 2.13.0 and a CVSS score of 4.0 for Oracle's issue.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
If upgrading is not immediately possible, applications can mitigate the issue by disabling exception message exposure to clients to avoid returning parsing exception messages in HTTP responses and/or disabling source inclusion in exceptions to prevent Jackson from embedding any source content in exception messages, avoiding leakage.
04

Evidence and provenance

Published 6 Jun 2025 · Last source change 9 Jun 2025, 15:13 UTC · CWE-209 · Generation of Error Message Containing Sensitive Information

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-17366
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2025-17366↗Vendor CSAF · Red Hat Product Security↗CISA Vulnrichment SSVC evidence↗CVE authority or vendor reference · GitHub GHSA-WF8F-6423-GFXG↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-49128 · cve.blacktree.nl