CVE-2026-19032
Received Received - Intake

Path Deserialization Flaw in Jackson-Databind

Vulnerability report for CVE-2026-19032, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-01

Last updated on: 2026-09-01

Assigner: HeroDevs

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-01
Last Modified
2026-09-01
Generated
2026-09-01
AI Q&A
2026-09-01
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 10 associated CPEs
Vendor Product Version / Range
fasterxml jackson-databind to 2.18.10 (exc)
fasterxml jackson-databind to 2.21.6 (exc)
fasterxml jackson-databind to 2.22.2 (exc)
fasterxml jackson-databind to 3.1.6 (exc)
fasterxml jackson-databind to 3.2.2 (exc)
fasterxml jackson-databind 2.18.10
fasterxml jackson-databind 2.21.6
fasterxml jackson-databind 2.22.2
fasterxml jackson-databind 3.1.6
fasterxml jackson-databind 3.2.2

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-470 The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.
CWE-610 The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in jackson-databind allows an attacker to bypass security restrictions during deserialization of java.nio.file.Path objects from untrusted JSON. The deserializer resolves attacker-supplied URIs without validating the URI scheme, potentially enabling unauthorized file system access if a malicious third-party FileSystemProvider is present on the classpath.

Detection Guidance

To detect this vulnerability, check if your system uses a vulnerable version of jackson-databind (2.8.0 to 2.18.9, 2.19.0 to 2.21.5, 2.22.0 to 2.22.1, 3.0.0 to 3.1.5, or 3.2.0 to 3.2.1). Run commands like: mvn dependency:tree | grep jackson-databind or gradle dependencies | grep jackson-databind to identify the version.

Impact Analysis

The impact depends on whether third-party FileSystemProviders with side effects are installed. Without such providers, the resolved path is inert. With malicious providers, an attacker could trigger network I/O, mount operations, or other filesystem actions by supplying crafted URIs during deserialization.

Mitigation Strategies

Upgrade jackson-databind to a patched version (2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2). Avoid binding java.nio.file.Path from untrusted JSON input. Review third-party FileSystemProvider implementations for potential risks.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-19032. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart