Vulnerability in axios (CVE-2026-44490)
Summary
Vulnerability in axios (CVE-2026-44490). Risk of unauthorized operations or information disclosure. Exploitable via Object.prototype. Mitigation: upgrade to 0.32.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. Prior to 0.32.0 and 1.16.0, axios exposes two read-side prototype-pollution gadgets. When Object.prototype is polluted by an upstream dependency in the same process (e.g. lodash _.merge / CVE-2018-16487), axios silently picks up the polluted values. (1) lib/utils.js line 406 builds merge()'s accumulator as result = {}, so result[targetKey] (line 414) walks Object.prototype and the polluted bucket's own keys are copied into the merged headers and ride out on the wire. (2) lib/core/mergeConfig.js line 26 builds the hasOwnProperty descriptor as a plain-object literal. Object.defineProperty reads descriptor.get/descriptor.set via the prototype chain, so a polluted Object.prototype.get or Object.prototype.set makes the call throw TypeError synchronously on every axios request. This vulnerability is fixed in 0.32.0 and 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-44490 has been found in axios.
Attackers can target a specific entry point like Object.prototype over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: upgrade axios to 0.32.0 or later.
If unsure, ask your IT team or search "axios CVE-2026-44490" on the vendor's site.
CVE-2026-44490 (axios) — CWE-1321 / CVSS v3 4.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Object.prototype / _.merge / hasOwnProperty / Object.defineProperty
Patched: 0.32.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-1321) exists in axios. Attackers reach the vulnerable code path via Object.prototype without authentication.
Check the vendor advisory for the affected versions of axios. Attack surface: Object.prototype / _.merge / hasOwnProperty / Object.defineProperty.
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure.
Update to 0.32.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 0.32.0ステージング環境で 0.32.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-44490 node-axios
- Ubuntu UBUNTU-CVE-2026-44490 node-axios
References
- advisory github.com
- advisory nvd.nist.gov
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com