CVE-2025-69202
mediumpriority · track · 26EPSS 0.003 · 24 %ileEUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 2.3–6.5
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (3)
Products and version ranges known to be affected.
- axios-cache-interceptor axios cache interceptor< 1.11.1nvdUScpe:2.3:a:axios-cache-interceptor:axios_cache_interceptor:*:*:*:*:*:*:*:*
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-x4m5-4cw8-vc44axios-cache-interceptor Vulnerable to Cache Poisoning via Ignored HTTP Vary Header2025-12-30ghsa · osvUS
## Summary When a server calls an upstream service using different auth tokens, axios-cache-interceptor returns incorrect cached responses, leading to authorization bypass. ## Details 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. ## Impact **Affected:** 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 - Upstream services replies on `Vary` to differentiate caches **Not affected:** Browser/client-side applications (single user per browser session). 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. ## Solution 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. ```js // v1.11.1+ (automatic, no config needed) // User 123: key = hash(url + {authorization: 'Bearer 123'}) // User 456: key = hash(url + {authorization: 'Bearer 456'}) // ✓ Different caches, no poisoning ``` ## Remediation Upgrade to v1.11.1 or later. _No code changes required, protection is automatic_ ## Proof of Concept ```js const http = require('node:http'); const axios = require('axios'); const { setupCache } = require('axios-cache-interceptor'); // Server that returns different responses based on Authorization const server = http.createServer((req, res) => { const auth = req.headers.authorization; res.setHeader('Vary', 'Authorization'); if (auth === 'Bearer 123') { res.write('Hello, user 123!'); } else if (auth === 'Bearer 456') { res.write('Hello, user 456!'); } else { res.write('Unknown'); } res.end(); }); server.listen(5000); // Client making requests with different tokens const cachedAxios = setupCache(axios.create()); const server2 = http.createServer(async (_req, res) => { const authHeader = Math.random() < 0.5 ? 'Bearer 123' : 'Bearer 456'; const response = await cachedAxios.get('http://localhost:5000', { headers: { Authorization: authHeader } }); console.log({ response: response.data, cached: response.cached, auth: authHeader }); res.write(response.data); res.end(); }); server2.listen(5001); // Trigger 10 requests Promise.all( Array.from({ length: 10 }, () => axios.get('http://localhost:5001').catch(console.error) ) ).finally(() => { server.close(); server2.close(); }); ``` All 10 responses return "Hello, user 123!" even when using "Bearer 456" - users receive each other's cached data.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (7)
External citations — patches, advisories, analysis.
- https://github.com/arthurfiorette/axios-cache-interceptor/commit/49a808059dfc081b9cc23d48f243d55dfce15f01cnnvd
- https://github.com/arthurfiorette/axios-cache-interceptor/releasesPatchcnnvd
- https://github.com/arthurfiorette/axios-cache-interceptor/security/advisories/GHSA-x4m5-4cw8-vc44cnnvd
- https://github.com/arthurfiorette/axios-cache-interceptor/commit/49a808059dfc081b9cc23d48f243d55dfce15f01enisa_euvd
- https://github.com/arthurfiorette/axios-cache-interceptor/security/advisories/GHSA-x4m5-4cw8-vc44enisa_euvd
- https://github.com/arthurfiorette/axios-cache-interceptor/commit/49a808059dfc081b9cc23d48f243d55dfce15f01Patchnvd
- https://github.com/arthurfiorette/axios-cache-interceptor/security/advisories/GHSA-x4m5-4cw8-vc44ExploitMitigationVendor Advisorynvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan