{"items":[{"id":"NVI-00006125","kind":"vulnerability","title":"Fix failure to strip Authorization header on HTTP downgrade","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-w248-ffj2-4v5q"],"plain_summary":"OSV carries this publisher advisory for guzzlehttp/guzzle, guzzlehttp/guzzle. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 6.5.7 for guzzlehttp/guzzle. Confirm the publisher’s latest guidance.","source_ids":["sr-a8936b5d2bbcabcbc9cae221bda2e089"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 7.4.4 for guzzlehttp/guzzle. Confirm the publisher’s latest guidance.","source_ids":["sr-a8936b5d2bbcabcbc9cae221bda2e089"],"action_type":"vendor_patch","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-a8936b5d2bbcabcbc9cae221bda2e089","url":"https://github.com/advisories/GHSA-w248-ffj2-4v5q","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-w248-ffj2-4v5q","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.380Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-a8936b5d2bbcabcbc9cae221bda2e089"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\n`Authorization` headers on requests are sensitive information. On making a request using the `https` scheme to a server which responds with a redirect to a URI with the `http` scheme, we should not forward the `Authorization` header on. This is much the same as to how we don't forward on the header if the host changes. Prior to this fix, `https` to `http` downgrades did not result in the `Authorization` header being removed, only changes to the host.\n\n### Patches\n\nAffected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4.\n\n### Workarounds\n\nAn alternative approach would be to use your own redirect middleware, rather than ours, if you are unable to upgrade. If you do not require or expect redirects to be followed, one should simply disable redirects all together.\n\n### References\n\n* RFC9110 Section 15.4\n\n### For more information\n\nIf you have any questions or comments about this advisory, please get in touch with us in `#guzzle` on the PHP HTTP Slack. Do not report addit","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 6.5.7"]},{"certainty":"source_listed","source_ids":["sr-a8936b5d2bbcabcbc9cae221bda2e089"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\n`Authorization` headers on requests are sensitive information. On making a request using the `https` scheme to a server which responds with a redirect to a URI with the `http` scheme, we should not forward the `Authorization` header on. This is much the same as to how we don't forward on the header if the host changes. Prior to this fix, `https` to `http` downgrades did not result in the `Authorization` header being removed, only changes to the host.\n\n### Patches\n\nAffected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4.\n\n### Workarounds\n\nAn alternative approach would be to use your own redirect middleware, rather than ours, if you are unable to upgrade. If you do not require or expect redirects to be followed, one should simply disable redirects all together.\n\n### References\n\n* RFC9110 Section 15.4\n\n### For more information\n\nIf you have any questions or comments about this advisory, please get in touch with us in `#guzzle` on the PHP HTTP Slack. Do not report addit","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.4"]}],"null_published_at":"2026-10-31T22:13:05.860Z","source_updated_at":"2025-12-10T23:40:57.755Z","source_disclosed_at":"2022-06-09T23:47:23.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-31T21:42:41.380Z"}],"next_cursor":null,"snapshot_revision":"42594"}