Vulnerabilities

Vulnerability · CVE-2026-19032

Path Deserialization Missing Scheme Allowlist for FileSystemProvider Resolution

Published Aug 21, 2026 · catalog updated Sep 1, 2026 · BSI

Last checked Nov 3, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-19032. EPSS is 0.57%. Act only if a listed version of BSI is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.57%
Remediation
Version ranges on file
Affected products
maven com.fasterxml.jackson.core:jackson-databind · maven tools.jackson.core:jackson-databind

### Summary A field bound from untrusted JSON reaches . The attacker string flows through → , then on into a enumeration that calls on the first scheme-matching provider. No scheme is rejected, so untrusted JSON can drive an arbitrary registered provider under the default . Impact is bounded. The JDK built-in providers ( , /zipfs) do no network I/O and do not mount, so the path is inert without a side-effecting third-party provider. Binding from untrusted input is already an anti-pattern. ### Description performs provider resolution driven by the attacker URI (abridged; the real method also handles a Windows drive-letter prefix and wraps failures via ): The attacker's scheme selects the provider and the attacker's URI is passed to it; the enumeration also forces provider classloading during . For built-in schemes like , throws (a mount requires explicit ), surfacing as a wrapped with no terminal effect. Any mount, network I/O, or resource access depends entirely on the selected provider. ## Vulnerable Code Location - - → ; body ( → → → ). ## Proof of Concept Two PoCs are provided. > PoC 2 registers a custom to show that attacker JSON reaches inside . Whether a third-party provider then does anything harmful is outside the library's control. The in-scope issue is **PoC 1** — the /arbitrary-scheme path reaching the fallback with no scheme restriction. **PoC 1 — sink reached (built-in provider).** : **PoC 2 — scheme-selection mechanism demo (custom ).** A third-party provider (scheme ) registered via , which is standing in for *any* provider a real application ships. : Registration descriptor — : Driver — : ## Execution Steps The PoCs need only the three Jackson 3.2.1 jars on the classpath and can be built with plain / . PoC 2 additionally requires the descriptor to be on the **runtime** classpath ## Reproduction Evidence Executed against jackson-databind 3.2.1 (OpenJDK 25). **PoC 1 :** Notes: the JDK **built-in** provider's does not auto-mount (it also throws , since

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • maven com.fasterxml.jackson.core:jackson-databind>= 2.19.0, < 2.21.6
  • maven com.fasterxml.jackson.core:jackson-databind>= 2.22.0, < 2.22.2
  • maven com.fasterxml.jackson.core:jackson-databind>= 2.8.0, < 2.18.10
  • maven tools.jackson.core:jackson-databind>= 3.0.0, < 3.1.6
  • maven tools.jackson.core:jackson-databind>= 3.2.0, < 3.2.2

How to fix CVE-2026-19032

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-19032. EPSS is 0.57%. Act only if a listed version of BSI is installed.

Which versions are affected?

Compare what you have installed with >= 2.19.0, < 2.21.6, >= 2.22.0, < 2.22.2, >= 2.8.0, < 2.18.10, >= 3.0.0, < 3.1.6, >= 3.2.0, < 3.2.2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-470; CWE-610. EPSS 0.57%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Sep 1, 2026 · Maintainer security tabs

    Updated

    ### Summary A field bound from untrusted JSON reaches . The attacker string flows through → , then on into a enumeration that calls on the first scheme-matching provider. No scheme is rejected, so untrusted JSON can drive an arbitrary registered provider under the default . Impact is bounded. The JDK built-in providers ( , /zipfs) do no network I/O and do not mount, so the path is inert without a

  2. Oct 30, 2026 · BSI CERT-Bund

    Detected

    CVE-2026-19032 is listed by SOS GmbH JobScheduler: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff.

Sources

  • BSI CERT-BundGovernment advisoryCVE-2026-19032

    SOS GmbH JobScheduler: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

    wid.cert-bund.de
  • CVE.orgVulnerability recordCVE-2026-19032

    Official CVE identifier

    cve.org
  • Maintainer security tabsVendor advisoryGHSA-wjgm-6hv5-3cvf

    ### Summary A field bound from untrusted JSON reaches . The attacker string flows through → , then on into a enumeration that calls on the first scheme-matching provider. No scheme is rejected, so untrusted JSON can drive an arbitrary registered provider under the default . Impact is bounded. The JDK built-in providers ( , /zipfs) do no network I/O and do not mount, so the path is inert without a

    github.com

Freshness

Last verified in this catalog Nov 3, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 2, 2026
  • CVE.orgOct 31, 2026
  • BSI CERT-BundOct 31, 2026