Uncontrolled Resource Consumption in Jackson-databind

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2022-42003: 3.41% estimated exploitation activity in the next 30 days; percentile 88.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

In FasterXML jackson-databind 2.4.0-rc1 until 2.12.7.1 and in 2.13.x before 2.13.4.2 resource exhaustion can occur because of a lack of a check in primitive value deserializers to avoid deep wrapper array nesting, when the UNWRAPSINGLEVALUEARRAYS feature is enabled. This was patched in 2.12.7.1, 2.13.4.2, and 2.14.0. Commits that introduced vulnerable code are https://github.com/FasterXML/jackson-databind/commit/d499f2e7bbc5ebd63af11e1f5cf1989fa323aa45, https://github.com/FasterXML/jackson-databind/commit/0e37a39502439ecbaa1a5b5188387c01bf7f7fa1, and https://github.com/FasterXML/jackson-databind/commit/7ba9ac5b87a9d6ac0d2815158ecbeb315ad4dcdc. Fix commits are https://github.com/FasterXML/jackson-databind/commit/cd090979b7ea78c75e4de8a4aed04f7e9fa8deea and https://github.com/FasterXML/jackson-databind/commit/d78d00ee7b5245b93103fef3187f70543d67ca33. The 2.13.4.1 release does fix this issue, however it also references a non-existent jackson-bom which causes build failures for gradle…

Published by the source

3 Oct 2022, 00:00 UTC

Last modified by the source

13 Sep 2024, 18:29 UTC

Source last checked

26 Oct 2026, 16:31 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jjjh-jjxp-wpff

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-42003

Advisory: Uncontrolled Resource Consumption in Jackson-databind
IDs: CVE-2022-42003, GHSA-jjjh-jjxp-wpff
Record: https://patchnext.com/advisories/cve-2022-42003 (revision 1, source checked 26 Oct 2026, 16:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.fasterxml.jackson.core:jackson-databind 2.13.4.2, 2.12.7.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.fasterxml.jackson.core:jackson-databind: affected >= 2.4.0-rc1, < 2.12.7.1; >= 2.13.0, < 2.13.4.2; fixed in 2.12.7.1, 2.13.4.2

## Suggested inspection (read-only)
- Maven com.fasterxml.jackson.core:jackson-databind: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.fasterxml.jackson.core:jackson-databind.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jjjh-jjxp-wpff (GitHub-reviewed advisory GHSA-jjjh-jjxp-wpff lists affected ranges: Maven com.fasterxml.jackson.core:jackson-databind >=2.4.0-rc1 =2.13.0 <2.13.4.2)

Commands are suggestions: review each one before running it.