Credential interception via unsynchronized shared proxy state
Published Jan 7, 2026 · Updated Jan 7, 2026
Race condition in axios4go before 0.6.4 allows remote attackers to route concurrent HTTP requests through an attacker-controlled proxy. Client.Request mutates the shared http.Client Transport, Timeout, and CheckRedirect fields without synchronization, so one request can inherit another request's proxy. Exploitation requires concurrent requests with differing proxy settings; the redirected request can expose credentials, tokens, and response data to the proxy.
Summary
What happened
Race condition in axios4go before 0.6.4 allows remote attackers to route concurrent HTTP requests through an attacker-controlled proxy. Client.Request mutates the shared http.Client Transport, Timeout, and CheckRedirect fields without synchronization, so one request can inherit another request's proxy. Exploitation requires concurrent requests with differing proxy settings; the redirected request can expose credentials, tokens, and response data to the proxy.
The record
- CVE
- CVE-2026-21697
- Published
- Jan 7, 2026
- Updated
- Jan 7, 2026
- Vendor
- Rez Moss
- Product
- axios4go
- Classifications
- CWE-362, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 7, 2026CVE publishedPublication date reported by the CVE source.
- Jan 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.6.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo