CVE-2026-21697: axios4go is a Go HTTP client library

Q: How do I fix CVE-2026-21697?

axios4go: upgrade to 0.6.4. Exact commands for each OS are on this page.

Q: Is CVE-2026-21697 being exploited?

CVE-2026-21697 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-21697 affect?

CVE-2026-21697 affects axios4go. Severity is high (CVSS 8.1). 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 mo

Q: How urgent is CVE-2026-21697?

Priority 42/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 8.1REMOTEUPGRADE

CVE-2026-21697 is a high-severity flaw (CVSS 8.1) affecting axios4go. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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`, `PostAs

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 65%)
CISA exploited list	No
Weakness	CWE-362
Published	2026-01-07
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: rezmoss

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-01-07 23:15 UTCPublished CVE record published
2026-06-17 10:18 UTCUpdated Record last modified

rezmoss axios4go UPGRADE

Affected: < 0.6.4

Fixed in: 0.6.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy axios4go || rpm -q axios4go || axios4go --version

2. UPGRADE to 0.6.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade axios4go

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade axios4go

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-21697?

axios4go: upgrade to 0.6.4. Exact commands for each OS are on this page.

Is CVE-2026-21697 being exploited?

CVE-2026-21697 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-21697 affect?

CVE-2026-21697 affects axios4go. Severity is high (CVSS 8.1). 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 mo

How urgent is CVE-2026-21697?

Priority 42/100. High severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs