Skip to main content
VulnerabilityPublished Updated

CVE-2025-69202: arthurfiorette axios-cache-interceptor · Use of Cache Containing Sensitive Information

Affects arthurfiorette axios-cache-interceptorSource CVE Database V5

0

Not known to be exploited · CVSS 6.0 Medium : upgrade to 1.11.1 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.11.1
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade arthurfiorette/axios-cache-interceptor to 1.11.1.

Affected software

ProductAffectedFixed in
npmarthurfiorette/axios-cache-interceptorpkg:npm/arthurfiorette/axios-cache-interceptorOther threatsAffected
  • <1.11.1
Fixed in
  • 1.11.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade axios-cache-interceptor to version 1.11.1 or later, where the vulnerability is fixed by including the Authorization header in cache keys when the upstream service responds with Vary: Authorization. Additionally, organizations should audit all backend services and API gateways that use axios-cache-interceptor or similar caching mechanisms to ensure proper handling of Vary headers and authorization tokens. Implement strict cache key generation policies that incorporate all headers affecting response content, especially Authorization. Conduct thorough code reviews and penetration testing focused on caching logic and authorization enforcement. Where possible, disable caching of sensitive authenticated responses or use cache partitioning per user session. Monitor logs for anomalous cache hits or unexpected data access patterns. Educate developers about the security implications of caching sensitive data and the importance of respecting HTTP caching semantics. Finally, maintain an inventory of all services using axios-cache-interceptor to ensure timely patching and compliance with data protection requirements.

Description

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.

References

Community reviews

Loading reviews…