← Search results
CVE-LINKED INVENTORY17 SECURITY RECORDS
FasterXML
jackson-databind
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-91777 | 23 Sep 2026 | jackson-databind: 2.5.0 ≤ 2.18.10, 2.19.0 ≤ 2.21.6, 2.22.0 ≤ 2.22.2, 3.0.0 ≤ 3.1.6, 3.2.0 ≤ 3.2.2 | Upgrade to com.fasterxml.jackson.core:jackson-databind 2.18.11, 2.21.7 or 2.22.3, or to tools.jackson.core:jackson-databind 3.1.7 or 3.2.3. Lines 2.5.x through 2.17.x, 2.19.x, 2.20.x and 3.0.x received no fix on their own branch and are no longer maintained upstream. | Update reference ↗ |
| CVE-2026-91776 | 23 Sep 2026 | jackson-databind: 2.0.0 ≤ 2.18.10, 2.19.0 ≤ 2.21.6, 2.22.0 ≤ 2.22.2, 3.0.0 ≤ 3.1.6, 3.2.0 ≤ 3.2.2 | Upgrade to com.fasterxml.jackson.core:jackson-databind 2.18.11, 2.21.7 or 2.22.3, or to tools.jackson.core:jackson-databind 3.1.7 or 3.2.3. Lines 2.0.x through 2.17.x, 2.19.x, 2.20.x and 3.0.x received no fix on their own branch and are no longer maintained upstream. | Update reference ↗ |
| CVE-2026-68497 | 11 Sep 2026 | jackson-databind: 2.0.0 < 2.18.10, 2.19.0 < 2.21.6, 2.22.0 < 2.22.2, 3.0.0 < 3.1.6, 3.2.0 < 3.2.2 | Upgrade to jackson-databind 2.18.10, 2.21.6, 2.22.2 (com.fasterxml.jackson.core) or 3.1.6, 3.2.2 (tools.jackson.core). The fix applies the same validate-length-then-parse idiom already used by NumberDeserializers, calling StreamReadConstraints length validation on the raw string before delegating to DatatypeFactory. The guard deliberately does not extend to javax.xml.namespace.QName, whose local parts may legitimately be long. | Update reference ↗ |
| CVE-2026-83557 | 1 Sep 2026 | 2.11.0 < 2.18.10; 2.19.0 < 2.21.6; 2.22.0 < 2.22.2; 3.0.0 < 3.1.6; 3.2.0 < 3.2.2 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-19032 | 1 Sep 2026 | 2.8.0 < 2.18.10; 2.19.0 < 2.21.6; 2.22.0 < 2.22.2; 3.0.0 < 3.1.6; 3.2.0 < 3.2.2 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-59889 | 14 Jul 2026 | >= 2.18.0, < 2.18.9; >= 2.21.0, < 2.21.5; >= 2.22.0, < 2.22.1; >= 3.0.0, < 3.1.5; >= 3.2.0, < 3.2.1 | Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-59888 | 14 Jul 2026 | >= 2.15.0, < 2.18.8; >= 2.19.0, < 2.21.4; >= 3.0.0, < 3.1.4 | For more information visit https://access.redhat.com/errata/RHSA-2026:68699 | Update reference ↗ |
| CVE-2026-54518 | 23 Jun 2026 | >= 2.21.0, < 2.21.4; >= 3.0.0, < 3.1.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-50193 | 23 Jun 2026 | >= 2.10.0, < 2.14.0 | Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-54512 | 23 Jun 2026 | >= 2.10.0, < 2.18.8; >= 2.19.0, < 2.21.4; >= 3.0.0, < 3.1.4 | Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-54513 | 23 Jun 2026 | jackson-databind: >= 2.10.0, < 2.18.8, >= 2.19.0, < 2.21.4, >= 3.0.0, < 3.1.4 | RHSA-2026:48095: Red Hat Certificate System 10.8 for RHEL 8 | Update reference ↗ |
| CVE-2026-54514 | 23 Jun 2026 | >= 2.0.0, < 2.18.8; >= 2.19.0, < 2.21.4; >= 3.0.0, < 3.1.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-54515 | 23 Jun 2026 | >= 2.8.0, < 2.18.9; >= 2.19.0, < 2.21.5; >= 3.1.0, < 3.1.4 | Before applying the update, make sure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-54516 | 23 Jun 2026 | >= 2.21.0, < 2.21.4; >= 3.0.0, < 3.1.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-54517 | 23 Jun 2026 | >= 2.21.0, < 2.21.4; >= 3.0.0, < 3.1.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-7525 | 6 Feb 2018 | before 2.6.7.1; before 2.7.9.1; before 2.8.9 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-15095 | 6 Feb 2018 | before 2.8.10; before 2.9.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.