CVE-2026-41698: Improper Entity Identifier Validation in Spring Vault Key/Value Accessors
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.
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.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
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.
Recent activity
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.