dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-59889

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
jackson-databind contains the general-purpose data-binding functionality and tree-model for Jackson Data Processor. From 2.18.0 until 2.18.9, 2.21.5, 2.22.1, 3.1.5, and 3.2.1, UnwrappedPropertyHandler.processUnwrapped() replays buffered JSON for a @JsonUnwrapped property and calls prop.deserializeAndSet() without a prop.visibleInView(ctxt.getActiveView()) guard, allowing a property annotated with both @JsonView and @JsonUnwrapped to be written from attacker JSON under a less-privileged active view. This issue is fixed in versions 2.18.9, 2.21.5, 2.22.1, 3.1.5, and 3.2.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The UnwrappedPropertyHandler.processUnwrapped() method in jackson-databind deserializes @JsonUnwrapped properties without checking @JsonView visibility controls, allowing attackers to modify fields that should be protected by view-based access control. This enables privilege escalation by injecting data into protected properties through unwrapped JSON structures.

MitigationUpgrade jackson-databind to version 2.18.9, 2.21.5, 2.22.1, 3.1.5, or 3.2.1 or later. If upgrade is not immediately possible, avoid using @JsonUnwrapped in combination with @JsonView on the same properties.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify jackson-databind version
    Locate the jackson-databind JAR file in your classpath or check your Maven pom.xml / Gradle build.gradle for the jackson-databind dependency and its version
    Affected if The installed version is earlier than 2.18.9, 2.21.5, 2.22.1, 3.1.5, or 3.2.1 (versions before the fixes)
  2. Search for @JsonUnwrapped usage
    Search your codebase for the @JsonUnwrapped annotation on POJO fields or methods
    Affected if @JsonUnwrapped is used on deserialized properties in your application
  3. Check for @JsonView on same properties
    Inspect classes containing @JsonUnwrapped fields to see if @JsonView is also applied to those same fields or their enclosing class
    Affected if @JsonView is applied alongside @JsonUnwrapped on the same properties, creating the vulnerable configuration
  4. Verify JSON deserialization of untrusted input
    Review code that uses ObjectMapper.readValue() or similar deserialization methods to determine if untrusted or external JSON input is processed
    Affected if Your application deserializes JSON from untrusted sources using ObjectMapper with classes containing the @JsonUnwrapped/@JsonView combination
  5. Review view-based access control enforcement
    Test whether view-based access controls are properly enforced when deserializing JSON into classes with @JsonUnwrapped properties
    Affected if Data in properties protected by @JsonView is unexpectedly accessible or modifiable through unwrapped JSON deserialization

You are affected if your jackson-databind version is before the fixed releases AND your application uses @JsonUnwrapped combined with @JsonView on the same properties to deserialize untrusted JSON.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade jackson-databind to version 2.18.9, 2.21.5, 2.22.1, 3.1.5, or 3.2.1 or later. If upgrade is not immediately possible, avoid using @JsonUnwrapped in combination with @JsonView on the same properties.

Recommended fix High confidence

2.18.9, 2.21.5, 2.22.1, 3.1.5, or 3.2.1 (choose the appropriate version for your branch)

  1. Identify the current jackson-databind version in use by checking pom.xml, build.gradle, or dependency management
  2. For 2.18.x branch: upgrade to 2.18.9
  3. For 2.21.x branch: upgrade to 2.21.5
  4. For 2.22.x branch: upgrade to 2.22.1
  5. For 3.1.x branch: upgrade to 3.1.5
  6. For 3.2.x branch: upgrade to 3.2.1
  7. Update the dependency in Maven (pom.xml) or Gradle (build.gradle) with the appropriate version
  8. Verify the upgrade by rebuilding the project and running tests
Caveat Minor release upgrades within the same major.minor branch typically have low risk, but review release notes for any behavior changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59889 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-59889 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data