Spring Vault Path Traversal via unsanitized secret path parameter

LOW | NOVEMBER 19, 2026 | CVE-2026-41698

Description

Spring Vault's Key/Value accessors perform no validation or normalization of the entity identifier argument before incorporating it into a Vault API URL. A caller-supplied value containing path traversal sequences is not rejected or sanitized and can cause Spring Vault to access or overwrite secrets outside the intended keyspace or mount, if those secrets are reachable by the application's Vault token.

Your application may be affected by this if all of the following are true:

  1. The application uses one of the affected repository or KeyValue accessor abstractions.
  2. The id value is derived from user-controlled input.
  3. The application's Vault token holds permissions beyond a single, tightly scoped keyspace path. Applications whose path values are determined entirely at build time are not affected.
  4. The application uses Vault 1.x. Vault 2.0 and later reject non-canonical or relative paths, so deployments using Vault 2.0 or later are not affected.

Affected Spring Products and Versions

Spring Vault:

  • 4.1.0 - 4.1.1
  • 4.0.0 - 4.0.4
  • 3.2.0 - 3.2.1
  • 3.0.0 - 3.1.3
  • 2.3.0 - 2.3.4

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.
Fix versionAvailability
4.1.2OSS
4.1.1.1Enterprise Support Only
4.0.5OSS
4.0.4.1Enterprise Support Only
3.2.2Enterprise Support Only
3.1.4Enterprise Support Only
2.3.5Enterprise Support Only

No further mitigation steps are necessary.

History

  • 2026-11-19: Initial vulnerability report published.

Get ahead

VMware offers training and certification to turbo-charge your progress.

Learn more

Get support

TrueSource Spring Enterprise offers support and binaries for OpenJDK™, Spring, and Apache Tomcat® in one simple subscription.

Learn more

Upcoming events

Check out all the upcoming events in the Spring community.

View all