Vulnerability in axios (CVE-2026-101902)
Summary
Vulnerability in axios (CVE-2026-101902). Risk of unauthorized operations or information disclosure. Exploitable via method. Mitigation: upgrade to 1.20.0 or later.
Original description
The description as published by the source.
Summary
Axios default-instance requests that omit an explicit method can read an inherited method value from Object.prototype. If another vulnerability in the same process pollutes Object.prototype.method, calls such as axios.request({ url }) and axios({ url }) can send a state-changing HTTP method instead of the expected default GET.
Axios does not create the prototype pollution source. This is a read-side gadget in axios request dispatch.
Impact
In an affected application with a separate prototype-pollution primitive, an attacker can change axios default-instance requests that omit method from GET to methods such as DELETE, POST, PUT, or PATCH. The practical impact depends on the target endpoint and can include unintended writes, deletion, or other state changes.
Method aliases such as axios.get(url) and requests with an explicit own method are not affected by the confirmed method path.
Affected Functionality
Affected:
- Default axios instance calls:
axios.request({ url }). - Callable shorthand:
axios({ url }). - Requests where no own
config.methodis provided.
Not affected in the confirmed method PoC:
axios.get(url)and other method aliases.axios.request({ url, method: 'GET' }).axios.create().request({ url })when the created instance defaults are produced by currentmergeConfig()and do not inherit fromObject.prototype.
Technical Details
lib/core/Axios.js sets the request method with:
co…
Source: NIST National Vulnerability Database 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-101902 has been found in axios.
Attackers can target a specific entry point like method over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade axios to 1.20.0 or later.
If unsure, ask your IT team or search "axios CVE-2026-101902" on the vendor's site.
CVE-2026-101902 (axios) — CWE-1321
Attack surface: method / Object.prototype / Object.prototype.method / GET
Patched: 1.20.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 method.
Check the vendor advisory for the affected versions of axios. Attack surface: method / Object.prototype / Object.prototype.method / GET.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.20.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.20.0ステージング環境で 1.20.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com