axios is vulnerable to read-side prototype-pollution gadgets that can alter request construction when Object.prototype has already been polluted by a separate vulnerability or dependency. In the bodyless method aliases (axios.get(), axios.delete(), axios.head(), axios.options()), inherited data is read via (config || {}).data before config normalization, causing an attacker-controlled body to be sent on requests that did not set one. Additional low-level paths, only reachable when calling exported adapters/helpers (e.g. lib/adapters/http.js, unsafe/helpers/resolveConfig.js) directly with plain configs and no own proxy or paramsSerializer, can inherit polluted proxy values (routing requests through an attacker-controlled proxy) or paramsSerializer values (attacker-controlled URL serialization). These low-level gadgets do not reproduce through normal high-level axios calls on 1.15.2+. The issue is fixed in axios 1.18.0 and 0.33.0.

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

  - axios is vulnerable to read-side prototype-pollution gadgets that can alter request construction when
    Object.prototype has already been polluted by a separate vulnerability or dependency. In the bodyless
    method aliases (axios.get(), axios.delete(), axios.head(), axios.options()), inherited data is read via
    (config || {}).data before config normalization, causing an attacker-controlled body to be sent on
    requests that did not set one. Additional low-level paths, only reachable when calling exported
    adapters/helpers (e.g. lib/adapters/http.js, unsafe/helpers/resolveConfig.js) directly with plain configs
    and no own proxy or paramsSerializer, can inherit polluted proxy values (routing requests through an
    attacker-controlled proxy) or paramsSerializer values (attacker-controlled URL serialization). These low-
    level gadgets do not reproduce through normal high-level axios calls on 1.15.2+. The issue is fixed in
    axios 1.18.0 and 0.33.0. (CVE-2026-67316)

The remote Fedora 43 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2026-625cbe86c8 advisory.

    34.0.3 Release

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

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

The remote Fedora 44 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2026-a1368a72b4 advisory.

    34.0.3 Release

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

Note that Nessus has not tested for these issues 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 prior to 0.33.0 or 1.x prior to 1.18.0. It is, therefore, affected by multiple vulnerabilities:

  - axios is vulnerable to read-side prototype-pollution gadgets that can alter request construction when     Object.prototype has already been polluted by a separate vulnerability or dependency. In the bodyless method     aliases, inherited data is read via (config || {}).data before config normalization, causing an     attacker-controlled body to be sent on requests that did not set one. (CVE-2026-67316)

  - axios can consume inherited properties from nested request option objects when the JavaScript process's     Object.prototype has already been polluted by another component. Nested plain objects such as auth and     paramsSerializer are cloned into ordinary objects and read without own-property checks. (CVE-2026-67319)

Note that Nessus has not tested for these issues 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 is vulnerable to read-side prototype-pollution gadgets that can alter request construction when     Object.prototype has already been polluted by a separate vulnerability or dependency. In the bodyless     method aliases (axios.get(), axios.delete(), axios.head(), axios.options()), inherited data is read via     (config || {}).data before config normalization, causing an attacker-controlled body to be sent on     requests that did not set one. Additional low-level paths, only reachable when calling exported     adapters/helpers (e.g. lib/adapters/http.js, unsafe/helpers/resolveConfig.js) directly with plain configs     and no own proxy or paramsSerializer, can inherit polluted proxy values (routing requests through an     attacker-controlled proxy) or paramsSerializer values (attacker-controlled URL serialization). These low-     level gadgets do not reproduce through normal high-level axios calls on 1.15.2+. The issue is fixed in     axios 1.18.0 and 0.33.0. (CVE-2026-67316)

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

ID	Name	Product	Family	Type	Severity
464826	Echo: axios: security update to 0.33.0	Tenable Cloud Security	Echo Local Security Checks	Local	medium
464826	Echo: axios: security update to 0.33.0	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	medium
339195	Fedora 43 : nextcloud (2026-625cbe86c8)	Nessus	Fedora Local Security Checks	Local	medium
339193	Fedora 44 : nextcloud (2026-a1368a72b4)	Nessus	Fedora Local Security Checks	Local	medium
333249	Node.js Module axios < 0.33.0 / 1.x < 1.18.0 Prototype Pollution	Nessus	Misc.	Local	medium
331634	Linux Distros Unpatched Vulnerability : CVE-2026-67316	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-67316

medium

Tenable Plugins

medium

medium

medium

medium

medium

medium