VulnerabilityPublished 1 Sep 2026Updated 6 Nov 2026

CVE-2026-19032: Libjackson json java · jackson-databind's deserializer for java.nio.file.Path resolves an

Affects libjackson-json-javaSource GCVE Database

Compare

Authoritative record:CVE-2026-19032· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium.

Data as of 6 Nov 2026, 15:25 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10libjackson-json-java`pkg:deb/ubuntu/libjackson-json-java?arch=source&distro=stonking`Other threats	Affected =1.9.13-2	Fixed in–
Ubuntu 20.04 LTSlibjackson-json-java`pkg:deb/ubuntu/libjackson-json-java?arch=source&distro=focal`Other threats	Affected =1.9.13-1	Fixed in–
Ubuntu 18.04 LTSlibjackson-json-java`pkg:deb/ubuntu/libjackson-json-java?arch=source&distro=bionic`Other threats	Affected =1.9.2-8 =1.9.2-9 =1.9.13-1~18.04	Fixed in–
Ubuntu Pro 14.04 LTSlibjackson-json-java`pkg:deb/ubuntu/libjackson-json-java?arch=source&distro=esm-infra-legacy/trusty`Other threats	Affected 1.9.2-1 – 1.9.2-3+deb8u1build0.14.04.1~esm1 4 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Fixed versions are available: upgrade to jackson-databind 2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2. Users should avoid binding java.nio.file.Path from untrusted JSON input regardless of version. No other specific mitigations are indicated.

Description

A vulnerability in jackson-databind's deserializer for java.nio.file.Path allows an attacker to supply a URI with an arbitrary scheme. This URI is resolved without restricting the scheme, potentially invoking a third-party FileSystemProvider. While the built-in JDK providers do not cause side effects, the presence of a malicious or side-effecting FileSystemProvider on the classpath could lead to unintended behavior. The issue affects multiple versions of jackson-databind and has been addressed in several patched releases. Users are advised to upgrade to the fixed versions and avoid binding java.nio.file.Path from untrusted JSON.

Impact

The vulnerability allows an attacker to influence the deserialization process to load an arbitrary FileSystemProvider based on a crafted URI scheme. While no direct confidentiality or integrity impact is reported, the forced loading of arbitrary providers could lead to denial of service or other side effects if a malicious or vulnerable third-party FileSystemProvider is present. With only standard JDK providers, the impact is limited to availability (application crash or denial of service). No known exploitation in the wild is reported.

Summary

The jackson-databind library's deserializer for java.nio.file.Path calls new URI(value) and then Path.of(uri) on attacker-controlled input without restricting the URI scheme. If Path.of(uri) throws FileSystemNotFoundException, the code enumerates ServiceLoader<FileSystemProvider> and calls getPath(uri) on the first provider matching the scheme. This allows untrusted JSON to select and drive an arbitrary registered FileSystemProvider during deserialization, forcing provider class loading. With only JDK built-in providers (file, jar/zipfs), the resolved path is inert and no network or mount I/O occurs. However, if a side-effecting third-party FileSystemProvider is present on the classpath, further impact is possible. The vulnerability affects com.fasterxml.jackson.core:jackson-databind versions 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, as well as 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 the fixed versions 2.18.10, 2.21.6, 2.22.2, 3.1.6, or 3.2.2. Binding java.nio.file.Path from untrusted JSON is discouraged regardless of version.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Nov 2026, 15:25 UTC

Technical details

References

Community reviews

Related threats