Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-44495 high CVSS 7.0

Code Injection in axios (CVE-2026-44495)

Summary

Code injection in axios (CVE-2026-44495). Confidential information can be exposed externally. Exploitable via Object.prototype.transformResponse. Mitigation: upgrade to 1.15.0 or later.

Original description

The description as published by the source.

Summary

Axios versions before the fixed releases contain prototype-pollution gadgets in request config processing. If another vulnerability in the same JavaScript process has already polluted Object.prototype.transformResponse, affected Axios versions may treat that inherited value as request configuration or as an option validator.

Axios does not itself create the prototype pollution. Exploitability requires a separate prototype-pollution vulnerability or equivalent attacker control over Object.prototype before Axios creates a request.

Impact

For ordinary prototype-pollution primitives that can only assign JSON-like values, this issue primarily results in request failures or denial-of-service attacks.

If the attacker can pollute Object.prototype.transformResponse with a function, affected versions of Axios may execute it. In fully affected versions, the function can observe response data and request config, including URL, headers, and auth, and can change the response data returned to application code.

This function-valued condition is important. Most query-string or JSON parser prototype-pollution bugs cannot create JavaScript functions on their own, so credential exposure and response tampering are conditional rather than automatic consequences of such bugs.

Affected Functionality

The affected functionality is Axios request config processing and response transformation.

Affected use requires all of the following:

  • An affected Axios version.
  • A pol…

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-44495 has been found in axios.
Attackers can target a specific entry point like Object.prototype.transformResponse over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.0/10.
What to do: upgrade axios to 1.15.0 or later.
If unsure, ask your IT team or search "axios CVE-2026-44495" on the vendor's site.

CVE-2026-44495 (axios) — CWE-94 / CVSS v3 7.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Object.prototype.transformResponse / Object.prototype / auth / transformResponse
Patched: 1.15.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.

❓ What is the problem

Arbitrary code execution (CWE-94) exists in axios. Attackers reach the vulnerable code path via Object.prototype.transformResponse without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of axios. Attack surface: Object.prototype.transformResponse / Object.prototype / auth / transformResponse.

🔥 Severity

Severity: High (CVSS 7.0/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.15.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify 
    grep -r 'axios' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で axios を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade axios to 1.15.0

    ステージング環境で 1.15.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm axios
[{"type":"SEMVER","events":[{"introduced":"0.19.0"},{"fixed":"0.31.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details