Skip to content

← Actionable
Medium, CVSS 6.5

jackson-databind has a @JsonView bypass for unwrapped creator parameters

CVE-2026-54518GHSA-rcqc-6cw3-h962

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (tools.jackson.core:jackson-databind 3.1.4; com.fasterxml.jackson.core:jackson-databind 2.21.4), 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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
  • CVE-2026-54518: 0.35% estimated exploitation activity in the next 30 days; percentile 29.20 (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 UnwrappedPropertyHandler.processUnwrappedCreatorProperties() replays buffered JSON into creator parameters but never consults prop.visibleInView(activeView). The normal property-based creator path gates creator properties on the active view, but this unwrapped-creator replay path bypasses that check, so a constructor parameter annotated with both @JsonView(AdminView.class) and @JsonUnwrapped is populated from attacker JSON even when a more restrictive view is active. Impact View-restricted unwrapped creator parameters can be set from untrusted input where @JsonView is used as a write-side authorization boundary. Affected / Patched (verified via git tag --contains) - 2.21 line: = 2.21.0, < 2.21.4 - fixed in 2.21.4 (backport 721fa07, #5973) - 3.x line: = 3.0.0, < 3.1.4 - fixed in 3.1.4 (#5971, d633bc0) Severity / CWE Maintainer: minor. Reporter: HIGH. CWE-863 (Incorrect Authorization); related CWE-284. Credits Omkhar Arasaratnam (@omkhar) - finder.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-rcqc-6cw3-h962

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-54518

Advisory: jackson-databind has a @JsonView bypass for unwrapped creator parameters
IDs: CVE-2026-54518, GHSA-rcqc-6cw3-h962
Record: https://patchnext.com/advisories/cve-2026-54518 (revision 1, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
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.1.4; com.fasterxml.jackson.core:jackson-databind 2.21.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven tools.jackson.core:jackson-databind: affected >= 3.0.0, < 3.1.4; fixed in 3.1.4
- Maven com.fasterxml.jackson.core:jackson-databind: affected >= 2.21.0, < 2.21.4; fixed in 2.21.4

## 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://github.com/advisories/GHSA-rcqc-6cw3-h962 (GitHub-reviewed advisory GHSA-rcqc-6cw3-h962 lists affected ranges: Maven com.fasterxml.jackson.core:jackson-databind >=2.21.0 =3.0.0 <3.1.4)

Commands are suggestions: review each one before running it.

Loading voting…