{"items":[{"id":"NVI-00014114","kind":"vulnerability","title":"Axios Node HTTP adapter can use an inherited proxy after interceptor config cloning","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-gcfj-64vw-6mp9","CVE-2026-67320"],"plain_summary":"GitHub lists this reviewed advisory for axios, axios. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-4a4d6e11205795a44d4d16f4d28e93d6"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-4a4d6e11205795a44d4d16f4d28e93d6","url":"https://github.com/advisories/GHSA-gcfj-64vw-6mp9","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-gcfj-64vw-6mp9","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T02:21:50.763Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4a4d6e11205795a44d4d16f4d28e93d6"],"technology":"axios","known_exclusions":[],"conditions_summary":"## Summary\n\nAxios’ Node.js HTTP adapter can route requests through an attacker-controlled proxy when `Object.prototype.proxy` is polluted and request configuration is materialized as a regular object before dispatch.\n\nRecent axios releases harden merged request config by creating a null-prototype object. However, request interceptors run after that merge and may return a replacement config. A common immutable interceptor pattern such as `{...config}` or `Object.assign({}, config)` converts the hardened config back into a normal object. Axios then dispatches that object without re-hardening it, and the Node HTTP adapter reads `config.proxy` through the prototype chain.\n\n## Impact\n\nIn a Node.js deployment using the HTTP adapter, an attacker who can trigger prototype pollution elsewhere in the process can route affected HTTP requests through an attacker-controlled proxy.\n\nThe highest confirmed impact is for plaintext HTTP requests. The proxy can observe explicit `Authorization` headers, axios-generated Basic auth from `config.auth`, request method, absolute URL, `Host`, and request body content. The proxy can also return its own response to axios for the affected request.\n\nThis does n","public_affected_ranges":[">= 0.31.1, < 0.33.0"]},{"certainty":"source_listed","source_ids":["sr-4a4d6e11205795a44d4d16f4d28e93d6"],"technology":"axios","known_exclusions":[],"conditions_summary":"## Summary\n\nAxios’ Node.js HTTP adapter can route requests through an attacker-controlled proxy when `Object.prototype.proxy` is polluted and request configuration is materialized as a regular object before dispatch.\n\nRecent axios releases harden merged request config by creating a null-prototype object. However, request interceptors run after that merge and may return a replacement config. A common immutable interceptor pattern such as `{...config}` or `Object.assign({}, config)` converts the hardened config back into a normal object. Axios then dispatches that object without re-hardening it, and the Node HTTP adapter reads `config.proxy` through the prototype chain.\n\n## Impact\n\nIn a Node.js deployment using the HTTP adapter, an attacker who can trigger prototype pollution elsewhere in the process can route affected HTTP requests through an attacker-controlled proxy.\n\nThe highest confirmed impact is for plaintext HTTP requests. The proxy can observe explicit `Authorization` headers, axios-generated Basic auth from `config.auth`, request method, absolute URL, `Host`, and request body content. The proxy can also return its own response to axios for the affected request.\n\nThis does n","public_affected_ranges":[">= 1.15.2, < 1.18.0"]}],"null_published_at":"2026-11-02T10:00:37.208Z","source_updated_at":"2026-09-01T18:42:33.000Z","source_disclosed_at":"2026-07-20T22:40:07.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-02T02:21:50.763Z"}],"next_cursor":null,"snapshot_revision":"42594"}