Vulnerability in axios (CVE-2026-44489)
Summary
Vulnerability in axios (CVE-2026-44489). Risk of unauthorized operations or information disclosure. Exploitable via Authorization header. Mitigation: upgrade to 1.16.0 or later.
Original description
The description as published by the source.
Axios is a promise based HTTP client for the browser and Node.js. From 1.15.2 to before 1.16.0, nested objects created by utils.merge() (e.g., config.proxy) are still constructed as plain {} with Object.prototype in their chain. The setProxy() function at lib/adapters/http.js:209-223 reads proxy.username, proxy.password, and proxy.auth without hasOwnProperty checks. When Object.prototype.username is polluted, setProxy() constructs a Proxy-Authorization header with attacker-controlled credentials and injects it into every proxied HTTP request. This vulnerability is fixed in 1.16.0.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44489 has been found in axios.
Attackers can target a specific entry point like Authorization header over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade axios to 1.16.0 or later.
If unsure, ask your IT team or search "axios CVE-2026-44489" on the vendor's site.
CVE-2026-44489 (axios) — CWE-113 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Authorization header / config.proxy / Object.prototype / proxy.username
Patched: 1.16.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-113) exists in axios. Attackers reach the vulnerable code path via Authorization header without authentication.
Check the vendor advisory for the affected versions of axios. Attack surface: Authorization header / config.proxy / Object.prototype / proxy.username.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to 1.16.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'axios' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'axios' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
axiosを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade axios to 1.16.0ステージング環境で 1.16.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-44489 node-axios Fixed in: 1.16.0-1
- Ubuntu UBUNTU-CVE-2026-44489 node-axios
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com