arthurfiorette axios-cache-interceptor up to 1.11.0 cache containing sensitive information

Summaryinfo

A vulnerability marked as problematic has been reported in arthurfiorette axios-cache-interceptor up to 1.11.0. This impacts an unknown function. The manipulation leads to use of cache containing sensitive information. This vulnerability is traded as CVE-2025-69202. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in arthurfiorette axios-cache-interceptor up to 1.11.0. This issue affects an unknown code. The manipulation with an unknown input leads to a use of cache containing sensitive information vulnerability. Using CWE to declare the problem leads to CWE-524. The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Axios Cache Interceptor is a cache interceptor for axios. Prior to version 1.11.1, when a server calls an upstream service using different auth tokens, axios-cache-interceptor returns incorrect cached responses, leading to authorization bypass. The cache key is generated only from the URL, ignoring request headers like `Authorization`. When the server responds with `Vary: Authorization` (indicating the response varies by auth token), the library ignores this, causing all requests to share the same cache regardless of authorization. Server-side applications (APIs, proxies, backend services) that use axios-cache-interceptor to cache requests to upstream services, handle requests from multiple users with different auth tokens, and upstream services replies on `Vary` to differentiate caches are affected. Browser/client-side applications (single user per browser session) are not affected. Services using different auth tokens to call upstream services will return incorrect cached data, bypassing authorization checks and leaking user data across different authenticated sessions. After `v1.11.1`, automatic `Vary` header support is now enabled by default. When server responds with `Vary: Authorization`, cache keys now include the authorization header value. Each user gets their own cache.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2025-69202 since 12/29/2025. The exploitation is known to be difficult. The attack may be initiated remotely. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

Upgrading to version 1.11.1 eliminates this vulnerability. Applying the patch 49a808059dfc081b9cc23d48f243d55dfce15f01 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-205645). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• arthurfiorette

Name

• axios-cache-interceptor

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11.0

License

• open-source

Website

• Product: https://github.com/arthurfiorette/axios-cache-interceptor/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion