CVE-2026-19032 jackson-databind resolves attacker-controlled URI schemes when deserializing java.nio.file.Path
Attackers can trigger arbitrary FileSystemProvider loading and potential code execution via crafted JSON in jackson-databind Path deserialization.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-19032?
CVE-2026-19032 is a medium-severity unsafe deserialization vulnerability in FasterXML jackson-databind, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Which versions are affected by CVE-2026-19032?
10 open source packages ship an affected version, including com.fasterxml.jackson.core:jackson-databind and tools.jackson.core:jackson-databind.
| Package | Affected | Fixed in |
|---|---|---|
com.fasterxml.jackson.core:jackson-databind Maven | From 2.19.0 | 2.21.6 |
com.fasterxml.jackson.core:jackson-databind Maven | From 2.19.0 | 2.21.6 |
com.fasterxml.jackson.core:jackson-databind Maven | From 2.22.0 | 2.22.2 |
com.fasterxml.jackson.core:jackson-databind Maven | From 2.22.0 | 2.22.2 |
com.fasterxml.jackson.core:jackson-databind Maven | From 2.8.0 | 2.18.10 |
com.fasterxml.jackson.core:jackson-databind Maven | From 2.8.0 | 2.18.10 |
4 more packages
tools.jackson.core:jackson-databind Maven | From 3.0.0 | 3.1.6 |
tools.jackson.core:jackson-databind Maven | From 3.0.0 | 3.1.6 |
tools.jackson.core:jackson-databind Maven | From 3.2.0 | 3.2.2 |
tools.jackson.core:jackson-databind Maven | From 3.2.0 | 3.2.2 |
How do I fix CVE-2026-19032?
Upgrade com.fasterxml.jackson.core:jackson-databind to a fixed version for your release line: 2.21.6, 2.22.2 or 2.18.10.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2026-19032 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19032 exists.
Sources
Also known as CLEANSTART-2026-AD83937, CLEANSTART-2026-BQ73969, CLEANSTART-2026-CZ82044, CLEANSTART-2026-DG88298, CLEANSTART-2026-FJ26239, CLEANSTART-2026-FO52414 and 125 more.