Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-67319 low CVSS 3.7

Vulnerability in axios (CVE-2026-67319)

Summary

Vulnerability in axios (CVE-2026-67319). Risk of unauthorized operations or information disclosure. Exploitable via Authorization header. Mitigation: upgrade to 1.18.0 or later.

Original description

The description as published by the source.

Summary

Axios can consume inherited properties from nested request option objects when the JavaScript process already has a polluted Object.prototype.

The top-level merged config is protected with a null prototype, but nested plain objects such as auth and paramsSerializer are cloned into ordinary objects. If application code passes placeholders such as auth: {} or paramsSerializer: {}, inherited username, password, encode, or serialize properties can influence outbound requests.

Impact

This is reachable only when another component has already polluted Object.prototype and the application passes an affected nested axios option object.

Confirmed impacts include silent injection of an Authorization: Basic ... header from inherited username and password values, and query-string tampering when inherited paramsSerializer fields are function-valued.

The auth case requires only string-valued pollution. Full query-string replacement through paramsSerializer.serialize requires a function-valued pollution primitive; string-only pollution may still cause request failures or encoding changes through encode.

This does not mean every axios request is affected. Requests that do not pass auth, do not pass paramsSerializer, or provide explicit own properties for the relevant nested fields are not affected by this specific gadget.

Affected Functionality

Affected runtime functionality:

  • Node HTTP adapter Basic auth handling in `lib/adapt…

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-67319 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.18.0 or later.
If unsure, ask your IT team or search "axios CVE-2026-67319" on the vendor's site.

CVE-2026-67319 (axios) — CWE-1321 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Authorization header / Object.prototype / auth / paramsSerializer
Patched: 1.18.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

A vulnerability (CWE-1321) exists in axios. Attackers reach the vulnerable code path via Authorization header without authentication.

📍 Affected scope

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

🔥 Severity

Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.18.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.18.0

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

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

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

Affected packages

npm axios
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.18.0"}]}]

References

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