chore(deps): update dependency axios-cache-interceptor to v1.11.1 [security] #117
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.8.3→1.11.1GitHub Vulnerability Alerts
CVE-2025-69202
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 withVary: 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:
Varyto differentiate cachesNot 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, automaticVaryheader 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.Remediation
Upgrade to v1.11.1 or later. No code changes required, protection is automatic
Proof of Concept
All 10 responses return "Hello, user 123!" even when using "Bearer 456" - users receive each other's cached data.
Release Notes
arthurfiorette/axios-cache-interceptor (axios-cache-interceptor)
v1.11.1Compare Source
Merged
#1157Commits
f88d836v1.11.0Compare Source
Merged
#1156#1155#1154#1153Commits
dc57ef59eec85d22aca7f3d6e7a5v1.10.0Compare Source
Merged
#1153v1.9.1Compare Source
Merged
#1144Commits
7204578fa82cd8v1.9.0Compare Source
Merged
#1140enabledflag for opt-in cache control#1141#1137#1138#1139#1106#1112#1134#1136#1135#1133#1132#1131#1130#1129#1128#1127#1126#1125#1124#1123#1122#1121#1119#1118#1117#1116#1115#1114#1109#1111#1107#1105#1104#1103#1102#1101#1100#1099#1097#1096#1093#1094#1095#1092Commits
cb80754Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.