CVE-2026-91776 Details
Description
TypeDeserializerBase._findDeserializer() in FasterXML jackson-databind caches the resolved deserializer under the raw, attacker-supplied type ID. When name-based polymorphism is configured with a fallback, for example @JsonTypeInfo(use = Id.NAME, defaultImpl = ...), every distinct unrecognized type ID resolves to the same fallback deserializer but is retained as its own key in the _deserializers map. That map has no configurable bound and lives for the lifetime of the type deserializer, so an attacker who can repeatedly supply fresh unknown type IDs causes monotonic memory retention across requests. The reporter observed 10,000 retained entries from 10,000 distinct unknown IDs, against a single entry for a control that repeated one unknown ID the same number of times, isolating attacker-controlled key cardinality from request volume. Exploitation requires an application that enables name-based polymorphism with a defaultImpl or equivalent fallback, accepts attacker-influenced type IDs, and reuses a long-lived ObjectMapper across requests. The fix stops caching fallback resolutions for unrecognized IDs and bounds both the number of cached entries and the length of a cacheable type ID.
A memory retention vulnerability has been identified in FasterXML Jackson-Databind versions 2.0.0 through 2.18.10, 2.19.0 through 2.21.6, and 2.22.0 through 2.22.2, as well as in tools.jackson.core:jackson-databind versions 3.0.0 through 3.1.6 and 3.2.0 through 3.2.2. The issue arises in the TypeDeserializerBase._findDeserializer() method, where the library caches resolved deserializers under attacker-supplied type IDs. This behavior is problematic when name-based polymorphism is used with a fallback deserializer, as each unrecognized type ID is mapped to the same fallback but retains its own entry in the deserializer cache. This unbounded caching can lead to increased memory usage and potential denial-of-service conditions.
Users can upgrade to Jackson-Databind versions 2.18.11, 2.21.7, 2.22.3, 3.1.7 or 3.2.3 to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Sep 23, 2026CISA-ADP
Assessed Sep 23, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/FasterXML/jackson-databind/security/advisories/GHSA-wv8q-qhhj-9h54 | CISA-ADP | AdvisoryExploitRemedyVendor |
| https://github.com/FasterXML/jackson-databind/issues/6203 | HeroDevs | Issue TrackingVendor |
| https://github.com/FasterXML/jackson-databind/security/advisories/GHSA-wv8q-qhhj-9h54 | HeroDevs | AdvisoryExploitRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-400 | Uncontrolled Resource Consumption | HeroDevs |
Affected Products
| Product | Versions |
|---|---|
| FasterXML jackson-databind | >= 2.0.0, <= 2.18.10 (semver) >= 2.19.0, <= 2.21.6 (semver) >= 2.22.0, <= 2.22.2 (semver) |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 23, 2026 | CVE Modified | CISA-ADP |
| Sep 23, 2026 | New CVE Received | HeroDevs |
Volerion