Skip to content

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

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

Medium Maven
Severity
6.5 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.35%
Chance of exploitation in the next 30 days. Higher than 29.17% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-863 Incorrect Authorization
Fix
Available
2 packages have a fixed version

Description

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.

Affected versions

Maven

PackageVulnerableFixed in
com.fasterxml.jackson.core:jackson-databind
>= 2.21.0, < 2.21.4
2.21.4
tools.jackson.core:jackson-databind
>= 3.0.0, < 3.1.4
3.1.4

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

com.fasterxml.jackson.core:jackson-databind Maven → 2.21.4

maven
<dependency><groupId>com.fasterxml.jackson.core</groupId><artifactId>jackson-databind</artifactId><version>2.21.4</version></dependency>
gradle
implementation("com.fasterxml.jackson.core:jackson-databind:2.21.4")

tools.jackson.core:jackson-databind Maven → 3.1.4

maven
<dependency><groupId>tools.jackson.core</groupId><artifactId>jackson-databind</artifactId><version>3.1.4</version></dependency>
gradle
implementation("tools.jackson.core:jackson-databind:3.1.4")

Severity breakdown

CVSS 3.1 6.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Weakness

CWE-863: Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

How to prevent it
  • Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Architecture and Design: Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
  • Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
  • Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
  • System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-cxp5-3px4-pw24
jackson-databind quadratic forward-reference completion
High Also affects com.fasterxml.jackson.core:jackson-databind
GHSA-wv8q-qhhj-9h54
jackson-databind retains every unknown raw type ID
High Also affects com.fasterxml.jackson.core:jackson-databind
GHSA-q4xh-88c3-wmh7
jackson-databind: Duration XMLGregorianCalendar Unbounded Number Parse DoS
High Also affects com.fasterxml.jackson.core:jackson-databind
GHSA-gx83-3vf8-gh7j
jackson-databind: Comparable missing from DefaultBaseTypeLimitingValidator's unsafe base types (incomplete PolymorphicTypeValidator denylist)
Medium Also affects com.fasterxml.jackson.core:jackson-databind
GHSA-wjgm-6hv5-3cvf
jackson-databind: Path Deserialization Missing Scheme Allowlist for FileSystemProvider Resolution
Medium Also affects com.fasterxml.jackson.core:jackson-databind
GHSA-vvgp-rfg2-7rr6
jackson-databind: Incomplete fix for CVE-2026-54514: eager DNS resolution (SSRF) still present in InetAddress deserialization
Medium Also affects com.fasterxml.jackson.core:jackson-databind
GHSA-mhm7-754m-9p8w
jackson-databind: `@JsonView` bypass for creator properties with `@JsonTypeInfo(include=As.EXTERNAL_PROPERTY)`
Medium Also affects com.fasterxml.jackson.core:jackson-databind
GHSA-5gvw-p9qm-jgwh
jackson-databind: @JsonView bypassed for @JsonUnwrapped container properties on deserialization
Medium Also affects com.fasterxml.jackson.core:jackson-databind
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor