jackson-databind: Path Deserialization Missing Scheme Allowlist for FileSystemProvider Resolution
CVE-2026-19032GHSA-wjgm-6hv5-3cvf
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (tools.jackson.core:jackson-databind 3.2.2, 3.1.6; com.fasterxml.jackson.core:jackson-databind 2.22.2, 2.21.6, 2.18.10), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven tools.jackson.core:jackson-databind
- Affected
- >= 3.0.0, < 3.1.6>= 3.2.0, < 3.2.2
- Fixed in
- 3.1.6, 3.2.2
Maven com.fasterxml.jackson.core:jackson-databind
- Affected
- >= 2.8.0, < 2.18.10>= 2.19.0, < 2.21.6>= 2.22.0, < 2.22.2
- Fixed in
- 2.22.2, 2.21.6, 2.18.10
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-wjgm-6hv5-3cvf lists affected ranges: Maven tools.jackson.core:jackson-databind >=3.0.0 =3.2.0 =2.8.0 =2.19.0 =2.22.0 <2.22.2 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-wjgm-6hv5-3cvf lists affected ranges: Maven tools.jackson.core:jackson-databind >=3.0.0 =3.2.0 =2.8.0 =2.19.0 =2.22.0 <2.22.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- EPSS
- CVE-2026-19032: 0.57% estimated exploitation activity in the next 30 days; percentile 47.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary A java.nio.file.Path field bound from untrusted JSON reaches JDKFromStringDeserializer.NioPathHelper.deserialize. The attacker string flows through new URI(value) → Path.of(uri), then on FileSystemNotFoundException into a ServiceLoader<FileSystemProvider enumeration that calls provider.getPath(uri) on the first scheme-matching provider. No scheme is rejected, so untrusted JSON can drive an arbitrary registered provider under the default JsonMapper.builder().build(). Impact is bounded. The JDK built-in providers (file, jar/zipfs) do no network I/O and do not mount, so the path is inert without a side-effecting third-party provider. Binding Path from untrusted input is already an anti-pattern. Description NioPathHelper.deserialize performs provider resolution driven by the attacker URI (abridged; the real method also handles a Windows drive-letter prefix and wraps failures via ctxt.handleInstantiationProblem(...)): The attacker's scheme selects the provider and the attacker's…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-wjgm-6hv5-3cvf
- Revision 1 · created ·
Published from osv record GHSA-wjgm-6hv5-3cvf
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-19032 Advisory: jackson-databind: Path Deserialization Missing Scheme Allowlist for FileSystemProvider Resolution IDs: CVE-2026-19032, GHSA-wjgm-6hv5-3cvf Record: https://patchnext.com/advisories/cve-2026-19032 (revision 2, source checked 26 Oct 2026, 16:56 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: tools.jackson.core:jackson-databind 3.2.2, 3.1.6; com.fasterxml.jackson.core:jackson-databind 2.22.2, 2.21.6, 2.18.10. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven tools.jackson.core:jackson-databind: affected >= 3.0.0, < 3.1.6; >= 3.2.0, < 3.2.2; fixed in 3.1.6, 3.2.2 - Maven com.fasterxml.jackson.core:jackson-databind: affected >= 2.8.0, < 2.18.10; >= 2.19.0, < 2.21.6; >= 2.22.0, < 2.22.2; fixed in 2.22.2, 2.21.6, 2.18.10 ## Suggested inspection (read-only) - Maven tools.jackson.core:jackson-databind: check the installed version with your package manager. - Maven com.fasterxml.jackson.core:jackson-databind: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on tools.jackson.core:jackson-databind, com.fasterxml.jackson.core:jackson-databind. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-wjgm-6hv5-3cvf (OSV record GHSA-wjgm-6hv5-3cvf lists affected ranges: Maven tools.jackson.core:jackson-databind >=3.0.0 =3.2.0 =2.8.0 =2.19.0 =2.22.0 <2.22.2 (fixed)) - Verified: https://github.com/advisories/GHSA-wjgm-6hv5-3cvf (GitHub-reviewed advisory GHSA-wjgm-6hv5-3cvf lists affected ranges: Maven tools.jackson.core:jackson-databind >=3.0.0 =3.2.0 =2.8.0 =2.19.0 =2.22.0 <2.22.2) Commands are suggestions: review each one before running it.
Loading voting…