Axios Cache Interceptor
Approved changes feed: RSS · Atom
cpe:2.3:a:arthurfiorette:axios-cache-interceptor:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Arthurfiorette (344fee04-65f2-508e-b7e9-dea9ec001da5) |
|---|---|
| Product | Axios Cache Interceptor (5facb06b-59b7-5235-87ad-f6bf8ce00f0a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/arthurfiorette/axios-cache-interceptor |
purl2cpe | 2026-06-01 10:13:03.300175 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-69202 |
vulnerable | 2026-06-08 07:41:22.180671 |
axios-cache-interceptor Vulnerable to Cache Poisoning via Ignored HTTP Vary Header
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.
Published: 2025-12-29T19:13:27.880Z
Updated: 2025-12-30T22:25:39.052Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.