rezmoss axios4go up to 0.6.3 Shared HTTP Client Configuration race condition

Summaryinfo

A vulnerability has been found in rezmoss axios4go up to 0.6.3 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component Shared HTTP Client Configuration Handler. This manipulation causes race condition. This vulnerability is handled as CVE-2026-21697. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as problematic was found in rezmoss axios4go up to 0.6.3. Affected by this vulnerability is an unknown part of the component Shared HTTP Client Configuration Handler. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect integrity. The summary by CVE is:

axios4go is a Go HTTP client library. Prior to version 0.6.4, a race condition vulnerability exists in the shared HTTP client configuration. The global `defaultClient` is mutated during request execution without synchronization, directly modifying the shared `http.Client`'s `Transport`, `Timeout`, and `CheckRedirect` properties. Impacted applications include that that use axios4go with concurrent requests (multiple goroutines, `GetAsync`, `PostAsync`, etc.), those where different requests use different proxy configurations, and those that handle sensitive data (authentication credentials, tokens, API keys). Version 0.6.4 fixes this issue.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-21697 since 01/02/2026. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

Upgrading to version 0.6.4 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch b651604c64e66a115ab90cdab358b0181d74a842 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-1381). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• rezmoss

Name

• axios4go

Version

• 0.6.0
• 0.6.1
• 0.6.2
• 0.6.3

License

• open-source

Website

• Product: https://github.com/rezmoss/axios4go/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion