Skip to main content
Mallory
UnratedVulnerability

CVE-2026-59377: Read-only association authorization bypass in Spring Data REST

Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-59377CWE-862

CVE-2026-59377 is an authorization vulnerability in Spring Data REST that permits modification of collection-like associations on aggregates intended to be read-only. Excluding a repository's save(…) method from REST export blocks PUT, PATCH, and DELETE operations on association resources, but POST requests bypass the corresponding authorization check. A POST request using text/uri-list can add referenced resources to an association and invoke the parent repository's save(…) method, persisting unauthorized association links.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker with access to affected association endpoints can compromise aggregate integrity by persisting association changes despite the repository's read-only REST configuration. The supplied severity assessment indicates high integrity impact, with no confidentiality or availability impact.

Mitigation

If you can’t patch tonight, do this now.

Restrict POST requests to association resources to trusted principals at the web security layer. Alternatively, remove the affected association from REST export by annotating its property with @RestResource(exported = false).

Remediation

Patch, then assume compromise.

Upgrade Spring Data REST to the corresponding fixed release. Open-source fixes are available in versions 5.1.3 and 5.0.9. Enterprise-support-only fixes are available in versions 5.1.2.1, 5.0.8.1, 4.5.15, 4.4.17, and 3.7.22.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-59377 exploited in the wild?
As of Nov 20, 2026, Mallory has no reports of CVE-2026-59377 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-59377?
As of Nov 20, 2026, Mallory has found no public exploit for CVE-2026-59377.
Is there a patch for CVE-2026-59377?
Upgrade Spring Data REST to the corresponding fixed release. Open-source fixes are available in versions 5.1.3 and 5.0.9.
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.