CVE-2026-19032: jackson-databind resolves attacker-controlled URI schemes when deserializing java.nio.file.Path
jackson-databind's deserializer for java.nio.file.Path resolves an attacker-supplied URI without restricting the URI scheme. In JDKFromStringDeserializer.NioPathHelper.deserialize, a string bound from untrusted JSON is passed to new URI(value) and then to Path.of(uri). When that throws FileSystemNotFoundException, the code enumerates ServiceLoader<FileSystemProvider> and calls provider.getPath(uri) on the first provider whose scheme matches the attacker-chosen scheme. Untrusted JSON can therefore select and drive an arbitrary registered FileSystemProvider during readValue under a default JsonMapper, and forces provider class loading at the same time. With only the JDK built-in providers (file, jar/zipfs) present, the resolved path is inert and no mount or network I/O occurs; further impact requires a side-effecting third-party FileSystemProvider on the classpath. This affects com.fasterxml.jackson.core:jackson-databind from 2.8.0 before 2.18.10, from 2.19.0 before 2.21.6, and from 2.22.0 before 2.22.2, and tools.jackson.core:jackson-databind from 3.0.0 before 3.1.6 and from 3.2.0 before 3.2.2. Users should upgrade to 2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2. Binding java.nio.file.Path from untrusted JSON should be avoided regardless of version.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
com.fasterxml.jackson.core:jackson-databindto a version that resolves this vulnerability.Fixed in 2.18.10 - Upgrade
Upgrade
com.fasterxml.jackson.core:jackson-databindto a version that resolves this vulnerability.Fixed in 2.21.6 - Upgrade
Upgrade
com.fasterxml.jackson.core:jackson-databindto a version that resolves this vulnerability.Fixed in 2.22.2 - Upgrade
Upgrade
tools.jackson.core:jackson-databindto a version that resolves this vulnerability.Fixed in 3.1.6 - Upgrade
Upgrade
tools.jackson.core:jackson-databindto a version that resolves this vulnerability.Fixed in 3.2.2 - Configuration
Upgrade/ensure the jackson-databind fix so the URI scheme allow-list defaults to "file" only; any scheme handling from untrusted JSON should be restricted to the allowed schemes.
JDK java.nio.file.Path binding from untrusted JSON URI scheme allow-list in JioPathDeserializer/NioPathHelper = defaults to "file" only - Compensating control
Avoid binding java.nio.file.Path from untrusted JSON (regardless of version). If applications legitimately need other schemes, construct NioPathDeserializer with an explicit collection of allowed schemes.
Event History
Frequently Asked Questions
Which deployments are meaningfully exposed beyond the default JDK setup?
Meaningful impact requires a side-effecting third-party FileSystemProvider on the application classpath. With only JDK built-in file and jar/zipfs providers, the resolved path is inert and does not cause mounting or network I/O.
What must an attacker be able to do to trigger the behavior?
An attacker must be able to supply untrusted JSON that is deserialized into a java.nio.file.Path during readValue. No authentication or user interaction is required by the listed vector.
Does the default JsonMapper configuration prevent this?
No. The issue can be triggered during readValue under a default JsonMapper when untrusted JSON is bound to java.nio.file.Path.
How can I assess whether a deployment has the higher-impact condition?
Identify whether the application deserializes untrusted JSON into java.nio.file.Path and whether any third-party FileSystemProvider implementations are present on its classpath. Such providers can be selected by an attacker-controlled URI scheme and are class-loaded during deserialization.
What versions should be used to remediate the issue?
Upgrade com.fasterxml.jackson.core:jackson-databind to 2.18.10, 2.21.6, or 2.22.2, as appropriate for the release line. Upgrade tools.jackson.core:jackson-databind to 3.1.6 or 3.2.2.