04 Affected products
PAIRS: —
01 RecordSTATE: PUBLISHED
02 Description
CNA: HeroDevsjackson-databind resolves attacker-controlled URI schemes when deserializing java.nio.file.Path
03 Exploitation and scoring
SRC: CISA, FIRST, NVD, RED HAT- Exploitation
- Not assessed. CISA has not published an exploitation assessment for this record, and it is not in the KEV catalog. That is an absence of assessment, not a finding of no risk.
- SSVC decision
- Not assessed by CISA
- EPSS probability
- Not scored by EPSS
- EPSS percentile
- Not scored by EPSS
- NVD base score
- The NVD has published no score for this record
- NVD CVSS vector
- No NVD score to derive
- NVD analysis status
- Not recorded
- Red Hat severity
- No Red Hat rating. Red Hat rates the CVEs that affect its products.
Exploit-prediction scores from FIRST. Independent scoring and analysis status from the NVD. Vendor severity from Red Hat. Exploitation assessment and catalog membership from CISA.
SCHEMA: 5.2
- Published
- 2026-09-01 03:18Z46 MIN AGO
- Last updated
- 2026-09-01 03:18Z46 MIN AGO
- Reserved
- 2026-08-06
- Assigning CNA
- HeroDevs
- Record state
- PUBLISHED
- Severity
- Medium (CVSS 5.3)
- CNA CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- Weaknesses
- CWE-470Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')Base
- CWE-610Externally Controlled Reference to a Resource in Another SphereClass
- Data version
- 5.2
- Document digest
- 3d614d8691c6ace5918ec479548fee8aa0851cf9ff7cfe88ded2703a2e7a40c9
05 Affected products
PAIRS: 1VendorProductVersionsPlatforms
FasterXMLjackson-databind2.8.0 to < 2.18.10, 2.19.0 to < 2.21.6, 2.22.0 to < 2.22.2, 3.0.0 to < 3.1.6, 3.2.0 to < 3.2.2— SRC: CNA
Upgrade to jackson-databind 2.18.10, 2.21.6, 2.22.2 (com.fasterxml.jackson.core) or 3.1.6, 3.2.2 (tools.jackson.core). The fix introduces a URI scheme allow-list that defaults to "file" only. Values with no scheme are still read as local filesystem paths. Any other scheme, including jar:, is rejected via handleWeirdStringValue before the ServiceLoader<FileSystemProvider> lookup is reached, so untrusted JSON can no longer select a provider. Applications that legitimately need other schemes can construct NioPathDeserializer with an explicit collection of allowed schemes. Note that this is a behavioral change: code that previously relied on non-file schemes being resolved will need to opt in.