Skip to main content
Mallory
UnratedVulnerability

CVE-2026-41698: Improper Entity Identifier Validation in Spring Vault Key/Value Accessors

Updated 2 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-41698CWE-20

Spring Vault's Key/Value accessors incorporate the entity identifier argument into a Vault API URL without validating or normalizing it. If an attacker can influence this argument, specially crafted identifiers may alter the intended request path or URL interpretation. Affected versions and the precise scope of request manipulation are not established.

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.

Attacker-controlled entity identifiers may cause Vault API requests to address unintended resources. Any resulting unauthorized access or modification depends on the accessor operation, URL handling, and permissions of the application's Vault token. Authentication bypass, arbitrary external request destinations, and specific confidentiality or integrity impacts are not established.

Mitigation

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

Prevent untrusted callers from directly supplying entity identifiers; map externally supplied references to approved Vault keys where feasible. Apply narrowly scoped Vault token policies to limit access to only required secret paths and operations.

Remediation

Patch, then assume compromise.

Validate entity identifiers against the application's intended key format before constructing Vault API URLs, and construct URLs so identifiers cannot change the intended API route. Preserve legitimate hierarchical key semantics where required. A vendor-confirmed fix and fixed release versions are not available in the supplied information.

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-41698 exploited in the wild?
As of Nov 20, 2026, Mallory has no reports of CVE-2026-41698 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-41698?
As of Nov 20, 2026, Mallory has found no public exploit for CVE-2026-41698.
Is there a patch for CVE-2026-41698?
Validate entity identifiers against the application's intended key format before constructing Vault API URLs, and construct URLs so identifiers cannot change the intended API route. Preserve legitimate hierarchical key semantics where required.
Activity feed

Recent activity

2 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 activity1Community discussion across Reddit, Mastodon, and other social sources.