CVE-2026-19032
Description
A flaw was found in jackson-databind. When deserializing java.nio.file.Path from untrusted JSON input, the deserializer resolves an attacker-supplied Uniform Resource Identifier (URI) without restricting the URI scheme. This allows a remote attacker to select and drive an arbitrary registered FileSystemProvider and force provider class loading. While the direct impact with only built-in Java Development Kit (JDK) providers is limited, the presence of a side-effecting third-party FileSystemProvider on the classpath could lead to further unintended consequences, such as resource access or network input/output (I/O).
Statement
Red Hat's CVSS score matches the upstream rating of Moderate (5.3). While this flaw allows an attacker to influence URI scheme resolution and force FileSystemProvider class loading during deserialization of java.nio.file.Path from untrusted JSON, the real-world impact is conditional: with only the standard JDK providers (file, jar/zipfs) present, the resolved path is inert and no network I/O or filesystem side effects occur. Meaningful exploitation requires a side-effecting third-party FileSystemProvider on the application classpath, which is not typical in production deployments. The availability impact is rated Low due to the possibility of triggering unexpected class loading. Red Hat agrees that the upstream rating accurately represents the risk in most deployment scenarios.
Mitigation
Avoid deserializing java.nio.file.Path from untrusted JSON input. If the application does not use Path deserialization, no remediation is required. Otherwise, upgrade jackson-databind to a fixed version: 2.18.10, 2.21.6, 2.22.2 (com.fasterxml.jackson.core), or 3.1.6 / 3.2.2 (tools.jackson.core).
As a workaround, register a custom deserializer for java.nio.file.Path that validates or rejects input before URI resolution, or configure the ObjectMapper to deny Path deserialization entirely.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.3 | N/A | 5.3 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | Low | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Application Data; Unexpected State
Attackers can modify unexpected objects or data that was assumed to be safe from modification. Deserialized data or code could be modified without using the provided accessor functions, or unexpected functions could be invoked.
Availability
Technical Impact: DoS: Resource Consumption (CPU)
If a function is making an assumption on when to terminate, based on a sentry in a string, it could easily never terminate.
Other
Technical Impact: Varies by Context
The consequences can vary widely, because it depends on which objects or methods are being deserialized, and how they are used. Making an assumption that the code in the deserialized object is valid is dangerous and can enable exploitation. One example is attackers using gadget chains to perform unauthorized actions, such as generating a shell.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
