CVE-2025-69202
Description
A flaw was found in axios-cache-interceptor, a caching plugin for the axios HTTP client. In versions prior to 1.11.1, the cache key was generated using only the request URL and did not include key headers such as Authorization. When an upstream service responds with the Vary: Authorization header — indicating that responses should differ based on the authorization token — this interceptor ignored that header and served the same cached response across different authenticated sessions. As a result, responses intended for one authenticated user could be returned to another user with a different token, resulting in authorization bypass and unintended disclosure of sensitive data.
Statement
Red Hat Product Security has determined that this vulnerability does not affect any currently supported Red Hat product. This assessment may evolve based on further analysis and discovery. For more information about this vulnerability and the products it affects, please see the linked references.
Mitigation
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism
Access control checks for specific user data or functionality can be bypassed.
Access Control
Technical Impact: Gain Privileges or Assume Identity
Horizontal escalation of privilege is possible (one user can view/modify information of another user).
Access Control
Technical Impact: Gain Privileges or Assume Identity
Vertical escalation of privilege is possible if the user-controlled key is actually a flag that indicates administrator status, allowing the attacker to gain administrative access.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
