{"items":[{"id":"NVI-00012132","kind":"vulnerability","title":"follow-redirects array-form headers bypass cross-origin credential stripping","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-q3jh-wrc6-jgq8","CVE-2026-111756"],"plain_summary":"GitHub lists this reviewed advisory for follow-redirects. 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-90831a5f2c1de6cf027d8d74a0248405"],"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":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.471%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.40769. Missing scores are unknown.","source_id":"sr-90831a5f2c1de6cf027d8d74a0248405"}],"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-b228cc36a0f9e9f3fe5356d75427700e","url":"https://github.com/advisories/GHSA-q3jh-wrc6-jgq8","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-q3jh-wrc6-jgq8","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:13:39.183Z"},{"id":"sr-90831a5f2c1de6cf027d8d74a0248405","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-111756","publisher":"FIRST EPSS","observed_at":"2026-11-01T01:39:43.066Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b228cc36a0f9e9f3fe5356d75427700e"],"technology":"follow-redirects","known_exclusions":[],"conditions_summary":"### Summary\nfollow-redirects removes sensitive credential headers (Authorization, Proxy-Authorization, Cookie, and any caller-declared `sensitiveHeaders`) before following a redirect that crosses to a different host or downgrades to a less secure protocol. The removal routine iterates the caller's headers container with `for...in` and matches header names against a filter. This assumes the headers container is a plain object keyed by header names. Node's underlying `http.request`, which follow-redirects is a drop-in replacement for, also accepts headers as an alternating array of names and values. For an array, `for...in` yields the numeric indices `\"0\"`, `\"1\"`, `\"2\"` and so on, which never match a header-name filter, so nothing is removed. An application that sends array-form headers and follows an attacker-controlled cross-origin redirect therefore forwards its Authorization, Cookie, and Proxy-Authorization headers verbatim to the attacker-controlled destination, with no error or warning. The `sensitiveHeaders` option added to fix CVE-2026-40895 / GHSA-r4q5-vmmm-2653 is equally ineffective, because it relies on the same helper. This is an unauthenticated confidentiality vulnerabi","public_affected_ranges":[">= 1.16.0, < 1.16.1"]}],"null_published_at":"2026-11-05T03:53:00.765Z","source_updated_at":"2026-10-20T17:58:08.000Z","source_disclosed_at":"2026-10-20T17:58:04.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T23:13:39.183Z"},{"id":"NVI-00012132","kind":"vulnerability","title":"follow-redirects array-form headers bypass cross-origin credential stripping","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-q3jh-wrc6-jgq8","CVE-2026-111756"],"plain_summary":"GitHub lists this reviewed advisory for follow-redirects. 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-b228cc36a0f9e9f3fe5356d75427700e"],"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-b228cc36a0f9e9f3fe5356d75427700e","url":"https://github.com/advisories/GHSA-q3jh-wrc6-jgq8","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-q3jh-wrc6-jgq8","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:13:39.183Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-b228cc36a0f9e9f3fe5356d75427700e"],"technology":"follow-redirects","known_exclusions":[],"conditions_summary":"### Summary\nfollow-redirects removes sensitive credential headers (Authorization, Proxy-Authorization, Cookie, and any caller-declared `sensitiveHeaders`) before following a redirect that crosses to a different host or downgrades to a less secure protocol. The removal routine iterates the caller's headers container with `for...in` and matches header names against a filter. This assumes the headers container is a plain object keyed by header names. Node's underlying `http.request`, which follow-redirects is a drop-in replacement for, also accepts headers as an alternating array of names and values. For an array, `for...in` yields the numeric indices `\"0\"`, `\"1\"`, `\"2\"` and so on, which never match a header-name filter, so nothing is removed. An application that sends array-form headers and follows an attacker-controlled cross-origin redirect therefore forwards its Authorization, Cookie, and Proxy-Authorization headers verbatim to the attacker-controlled destination, with no error or warning. The `sensitiveHeaders` option added to fix CVE-2026-40895 / GHSA-r4q5-vmmm-2653 is equally ineffective, because it relies on the same helper. This is an unauthenticated confidentiality vulnerabi","public_affected_ranges":[">= 1.16.0, < 1.16.1"]}],"null_published_at":"2026-11-01T01:04:01.244Z","source_updated_at":"2026-10-20T17:58:08.000Z","source_disclosed_at":"2026-10-20T17:58:04.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-10-31T23:13:39.183Z"}],"next_cursor":null,"snapshot_revision":"42594"}