jackson-databind resolves attacker-controlled URI schemes when deserializing java.nio.file.Path
FasterXML · jackson-databind
5.3MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix
Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 289 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Published severityMedium→Operational priority:High, raised one band.upgradedsince 1 Sep 2026
Evidence used
No CISA KEV confirmation is currently recorded.
A structured source references public exploit or proof-of-concept material.
The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
EPSS is 0.53% for the current model date.
Compensating controls
Validate the affected product branch and deploy the verified fixed release.
Restrict the affected network interface to trusted sources where business-safe.
Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
Confirm that the asset runs FasterXML jackson-databind and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Cross-source reconciliation
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 289 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Red Hat Product Security: 285 affected or under-investigation product states without a fixed product state in the same current advisory
Debian Security Tracker: 4 affected package states with no published fix
Distribution package intelligence
Release-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
5 package states
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
Distribution release
Source package
Vendor state
Fixed version
Evidence
Debian trixietrixie · source
jackson-databind
Affected, no fix publishedDebian currently tracks this release as open.
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products as affected by this CVE.
jackson-databind as component of SUSE Linux Enterprise High Performance Computing 15 SP2
jackson-databind as component of SUSE Linux Enterprise High Performance Computing 15 SP3
jackson-databind-javadoc as component of SUSE Linux Enterprise High Performance Computing 15 SP3
jackson-databind as component of SUSE Linux Enterprise Server 15 SP2-LTSS
jackson-databind as component of SUSE Linux Enterprise Server 15 SP2
jackson-databind as component of SUSE Linux Enterprise Server 15 SP3-LTSS
jackson-databind-javadoc as component of SUSE Linux Enterprise Server 15 SP3-LTSS
jackson-databind as component of SUSE Linux Enterprise Server 15 SP3
jackson-databind-javadoc as component of SUSE Linux Enterprise Server 15 SP3
jackson-databind as component of SUSE Linux Enterprise Server 16.0
jackson-databind-javadoc as component of SUSE Linux Enterprise Server 16.0
jackson-databind as component of SUSE Linux Enterprise Server 16.1
Summary
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 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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-19032 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitycom.fasterxml.jackson.core/jackson-databind: tools.jackson.core/jackson-databind: Jackson-databind: Uncontrolled URI scheme resolution in Path deserialization
285 known affected
The vendor explicitly identifies these products as affected by this CVE.
exploit-intelligence/agent-client-rhel9 as a component of Exploit Intelligence
jenkins-2-plugins.src as a component of OpenShift Developer Tools and Services
jenkins.src as a component of OpenShift Developer Tools and Services
ocp-tools-4/jenkins-rhel8 as a component of OpenShift Developer Tools and Services
ocp-tools-4/jenkins-rhel9 as a component of OpenShift Developer Tools and Services
openshift-serverless-1/kn-ekb-dispatcher-rhel9 as a component of OpenShift Serverless
openshift-serverless-1/kn-ekb-receiver-rhel9 as a component of OpenShift Serverless
openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9 as a component of OpenShift Serverless
openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9 as a component of OpenShift Serverless
openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9 as a component of OpenShift Serverless
openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9 as a component of OpenShift Serverless
openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9 as a component of OpenShift Serverless
Summary
A flaw was found in jackson-databind. When deserializing java.nio.file.Path from untrusted JSON input, the deserializer resolves an attacker-supplied Uniform Resource Identifier (URI) without restricting the URI scheme. This allows a remote attacker to select and drive an arbitrary registered FileSystemProvider and force provider class loading. While the direct impact with only built-in Java Development Kit (JDK) providers is limited, the presence of a side-effecting third-party FileSystemProvider on the classpath could lead to further unintended consequences, such as resource access or network input/output (I/O).
Remediation
Avoid deserializing java.nio.file.Path from untrusted JSON input. If the application does not use Path deserialization, no remediation is required. Otherwise, upgrade jackson-databind to a fixed version: 2.18.10, 2.21.6, 2.22.2 (com.fasterxml.jackson.core), or 3.1.6 / 3.2.2 (tools.jackson.core). As a workaround, register a custom deserializer for java.nio.file.Path that validates or rejects input before URI resolution, or configure the ObjectMapper to deny Path deserialization entirely.
Optional official sources
National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.
Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.
Official European source
ENISA European Vulnerability Database
Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.
1 current
ENISA EUVD identifier
EUVD-2026-68961
No EUVD known-exploited evidence
jackson-databind: Path Deserialization Missing Scheme Allowlist for FileSystemProvider Resolution
EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
5.3 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix
Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 289 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product
01
What, why and how
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.
What
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.
Why
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.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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.
Why
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.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No confirmed evidence
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.Reference recorded
CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.
Likely attack path
a network path → Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness ?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection'). 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.
CVSS vector ?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
Operational remediation based on structured source evidence.
Status ?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 1 Sept 2026 · Last source change 1 Sept 2026, 13:13 UTC · CWE-470 · Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source ?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.FIRST · tracked since 2026-09-01
European sourceENISA EUVD · EUVD-2026-68961
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Affected versionsThe structured affected or fixed version information changed.
Before
jackson-databind as component of SUSE Linux Enterprise Desktop 15 SP7; jackson-databind as component of SUSE Linux Enterprise High Performance Computing 15 SP2; jackson-databind as component of SUSE Linux Enterprise High Performance Computing 15 SP3; jackson-databind-javadoc as component of SUSE Linux Enterprise High Performance Computing 15 SP3; jackson-databind as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS; jackson-databind as component of SUSE Linux Enterprise High Performance Computing 15 SP4; jackson-databind as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS; jackson-databind as component of SUSE Linux Enterprise High Performance Computing 15 SP5; jackson-databind as component of SUSE Linux Enterprise Module for Basesystem 15 SP7; jackson-databind as component of SUSE Linux Enterprise Server 15 SP2-LTSS; jackson-databind as component of SUSE Linux Enterprise Server 15 SP2; jackson-databind as component of SUSE Linux Enterprise Server 15 SP3-LTSS; jackson-databind-javadoc as component of SUSE Linux Enterprise Server 15 SP3-LTSS; jackson-databind as component of SUSE Linux Enterprise Server 15 SP3; jackson-databind-javadoc as component of SUSE Linux Enterprise Server 15 SP3; jackson-databind as component of SUSE Linux Enterprise Server 15 SP4-LTSS; jackson-databind as component of SUSE Linux Enterprise Server 15 SP4; jackson-databind as component of SUSE Linux Enterprise Server 15 SP5-LTSS; jackson-databind as component of SUSE Linux Enterprise Server 15 SP5; jackson-databind as component of SUSE Linux Enterprise Server 15 SP6-LTSS; jackson-databind as component of SUSE Linux Enterprise Server 15 SP6; jackson-databind as component of SUSE Linux Enterprise Server 15 SP7; jackson-databind as component of SUSE Linux Enterprise Server 16.0; jackson-databind-javadoc as component of SUSE Linux Enterprise Server 16.0; jackson-databind as component of SUSE Linux Enterprise Server 16.1; jackson-databind-javadoc as component of SUSE Linux Enterprise Server 16.1; jackson-databind as component of SUSE Linux Enterprise Server Teradata 15 SP4; jackson-databind as component of SUSE Linux Enterprise Server for SAP Applications 15 SP2; jackson-databind as component of SUSE Linux Enterprise Server for SAP Applications 15 SP3; jackson-databind-javadoc as component of SUSE Linux Enterprise Server for SAP Applications 15 SP3; and 9 more
After
jackson-databind as component of SUSE Linux Enterprise High Performance Computing 15 SP2; jackson-databind as component of SUSE Linux Enterprise High Performance Computing 15 SP3; jackson-databind-javadoc as component of SUSE Linux Enterprise High Performance Computing 15 SP3; jackson-databind as component of SUSE Linux Enterprise Server 15 SP2-LTSS; jackson-databind as component of SUSE Linux Enterprise Server 15 SP2; jackson-databind as component of SUSE Linux Enterprise Server 15 SP3-LTSS; jackson-databind-javadoc as component of SUSE Linux Enterprise Server 15 SP3-LTSS; jackson-databind as component of SUSE Linux Enterprise Server 15 SP3; jackson-databind-javadoc as component of SUSE Linux Enterprise Server 15 SP3; jackson-databind as component of SUSE Linux Enterprise Server 16.0; jackson-databind-javadoc as component of SUSE Linux Enterprise Server 16.0; jackson-databind as component of SUSE Linux Enterprise Server 16.1; jackson-databind-javadoc as component of SUSE Linux Enterprise Server 16.1; jackson-databind as component of SUSE Linux Enterprise Server for SAP Applications 15 SP2; jackson-databind as component of SUSE Linux Enterprise Server for SAP Applications 15 SP3; jackson-databind-javadoc as component of SUSE Linux Enterprise Server for SAP Applications 15 SP3; jackson-databind as component of SUSE Linux Enterprise Server for SAP applications 16.0; jackson-databind-javadoc as component of SUSE Linux Enterprise Server for SAP applications 16.0; jackson-databind as component of SUSE Linux Enterprise Server for SAP applications 16.1; jackson-databind-javadoc as component of SUSE Linux Enterprise Server for SAP applications 16.1; jackson-databind as component of openSUSE Leap 16.0
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.