{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-21697 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-21697 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-21697 is a high-severity vulnerability in rezmoss axios4go, published on 7 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-21697 and fix it if it is affected.\n\nWhat it is: CVE-2026-21697 is a high-severity vulnerability in rezmoss axios4go, published on 7 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-21697 in the wild and no public exploit code.\n\nAffected product: rezmoss axios4go. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-21697/ (Markdown: https://insights.sbomify.com/CVE-2026-21697/index.md)","id":"CVE-2026-21697","markdown":"https://insights.sbomify.com/CVE-2026-21697/index.md","name":"CVE-2026-21697","record":{"aliases":["GHSA-cmj9-27wj-7x47"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Go HTTP client library","requires_auth":"none","summary":"A race condition in axios4go allows attackers to leak proxy configurations and potentially bypass security controls in concurrent applications.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"axios4go","vendor":"rezmoss"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"axios4go's Race Condition in Shared HTTP Client Allows Proxy Configuration Leak","id":"CVE-2026-21697","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"SQL injection in Backup and Replication","id":"CVE-2026-21708"},"packages":[],"prev":{"headline":"Endless reprocessing/reupload of activity log data due to SQLite max parameters limit not being considered","id":"CVE-2026-21696"},"products":["axios4go"],"published":"2026-01-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-08","vendors":["rezmoss"]},"summary":"A race condition in axios4go allows attackers to leak proxy configurations and potentially bypass security controls in concurrent applications.","url":"https://insights.sbomify.com/CVE-2026-21697/"}