CVE-2026-19032

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).

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.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.

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.