axios in a Node.js deployment using the HTTP adapter can route requests through an attacker-controlled proxy. axios hardens merged request configuration by creating a null-prototype object, but request interceptors run after the merge; a common immutable interceptor pattern such as {...config} or Object.assign({}, config) converts the hardened config back into a regular object. axios then dispatches that object without re-hardening it, and the Node HTTP adapter reads config.proxy through the prototype chain. If an attacker can pollute Object.prototype.proxy, affected requests can be routed through an attacker-controlled proxy. For plaintext HTTP requests, the proxy can observe Authorization headers, Basic auth from config.auth, method, absolute URL, Host, and request body, and can return its own response. This does not establish browser impact or HTTPS header/body disclosure under normal TLS validation. Affected versions are >=0.31.1 (fixed in 0.33.0) and >=1.15.2 (fixed in 1.18.0).

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - axios in a Node.js deployment using the HTTP adapter can route requests through an attacker-controlled
    proxy. axios hardens merged request configuration by creating a null-prototype object, but request
    interceptors run after the merge; a common immutable interceptor pattern such as {...config} or
    Object.assign({}, config) converts the hardened config back into a regular object. axios then dispatches
    that object without re-hardening it, and the Node HTTP adapter reads config.proxy through the prototype
    chain. If an attacker can pollute Object.prototype.proxy, affected requests can be routed through an
    attacker-controlled proxy. For plaintext HTTP requests, the proxy can observe Authorization headers, Basic
    auth from config.auth, method, absolute URL, Host, and request body, and can return its own response. This
    does not establish browser impact or HTTPS header/body disclosure under normal TLS validation. Affected
    versions are >=0.31.1 (fixed in 0.33.0) and >=1.15.2 (fixed in 1.18.0). (CVE-2026-67320)

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the TSSA-2026:0822 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2026-67320:
    axios in a Node.js deployment using the HTTP adapter can route requests through an attacker-controlled     proxy. axios hardens merged request configuration by creating a null-prototype object, but request     interceptors run after the merge; a common immutable interceptor pattern such as {...config} or     Object.assign({}, config) converts the hardened config back into a regular object. axios then dispatches     that object without re-hardening it, and the Node HTTP adapter reads config.proxy through the prototype     chain. If an attacker can pollute Object.prototype.proxy, affected requests can be routed through an     attacker-controlled proxy.

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of the axios Node.js module installed on the remote host is 0.31.1 prior to 0.33.0 or 1.15.2 prior to 1.18.0. It is, therefore, affected by a vulnerability:

  - axios in a Node.js deployment using the HTTP adapter can route requests through an attacker-controlled     proxy. Request interceptors run after the merge and a common immutable interceptor pattern converts the     hardened config back into a regular object. The Node HTTP adapter then reads config.proxy through the     prototype chain, allowing an attacker who can pollute Object.prototype.proxy to observe Authorization     headers, Basic auth, and request bodies on plaintext HTTP requests. (CVE-2026-67320)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - axios in a Node.js deployment using the HTTP adapter can route requests through an attacker-controlled     proxy. axios hardens merged request configuration by creating a null-prototype object, but request     interceptors run after the merge; a common immutable interceptor pattern such as {...config} or     Object.assign({}, config) converts the hardened config back into a regular object. axios then dispatches     that object without re-hardening it, and the Node HTTP adapter reads config.proxy through the prototype     chain. If an attacker can pollute Object.prototype.proxy, affected requests can be routed through an     attacker-controlled proxy. For plaintext HTTP requests, the proxy can observe Authorization headers, Basic     auth from config.auth, method, absolute URL, Host, and request body, and can return its own response. This     does not establish browser impact or HTTPS header/body disclosure under normal TLS validation. Affected     versions are >=0.31.1 (fixed in 0.33.0) and >=1.15.2 (fixed in 1.18.0). (CVE-2026-67320)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
457859	Echo: axios: security update to 0.33.0	Tenable Cloud Security	Echo Local Security Checks	Local	high
457859	Echo: axios: security update to 0.33.0	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	high
334827	TencentOS Server 4: grafana (TSSA-2026:0822)	Nessus	Tencent Local Security Checks	Local	high
333250	Node.js Module axios 0.31.1 < 0.33.0 / 1.15.2 < 1.18.0 Proxy Hijacking (CVE-2026-67320)	Nessus	Misc.	Local	high
331637	Linux Distros Unpatched Vulnerability : CVE-2026-67320	Nessus	Misc.	Local	high

Detections

Analytics

CVE-2026-67320

high

Tenable Plugins

high

high

high

high

high