Spring Cloud Gateway LocalResponseCache Stores private and no-store Responses, Leaking Authenticated Content

HIGH | NOVEMBER 19, 2026 | CVE-2026-59427

Description

Spring Cloud Gateway's LocalResponseCache decides whether an upstream response may be stored by comparing each complete Cache-Control header value with the strings private and no-store, instead of parsing the comma-separated directives. A protected upstream response with a combined value, such as private, no-store or the Spring Security default no-cache, no-store, max-age=0, must-revalidate, is therefore stored in the route cache even though the upstream prohibited it. A later request can then be served that cached response without reaching the upstream, so an unauthenticated attacker can read content that was meant for an authenticated user.

Applications are affected only if LocalResponseCache is enabled on a route that forwards to an upstream that returns user-specific or otherwise private responses with a Cache-Control header containing more than one directive, and the upstream does not distinguish callers with a Vary header.

Affected Spring Products and Versions

Spring Cloud Gateway:

  • 5.0.0 - 5.0.4
  • 4.3.0 - 4.3.6
  • 4.0.0 - 4.2.10

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.
Fix versionAvailability
5.0.5OSS
5.0.4.1Enterprise Support Only
4.3.7Enterprise Support Only
4.2.11Enterprise Support Only

No further mitigation steps are necessary.

Credit

This vulnerability was discovered and responsibly reported by hussst and Yu Yicheng.

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