{"items":[{"id":"NVI-00004131","kind":"vulnerability","title":"CURLOPT_HTTPAUTH option not cleared on change of origin","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-25mq-v84q-4j7r","CVE-2022-31090"],"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.8 for guzzlehttp/guzzle. Confirm the publisher’s latest guidance.","source_ids":["sr-59557c9d6b271a21e1a0c5472f86fa91"],"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.5 for guzzlehttp/guzzle. Confirm the publisher’s latest guidance.","source_ids":["sr-59557c9d6b271a21e1a0c5472f86fa91"],"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":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-5488f3b109b9d417d0648edca794f196"],"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":"CVSS","as_of":"2026-06-17T04:44:46.550Z","value":"4 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-d34ae8d3cfc52d1130e77d5a122fc249"},{"kind":"CVSS","as_of":"2026-06-17T04:44:46.550Z","value":"7.7 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-d34ae8d3cfc52d1130e77d5a122fc249"},{"kind":"CVSS","as_of":"2026-06-17T04:44:46.550Z","value":"7.7 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-d34ae8d3cfc52d1130e77d5a122fc249"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"1.916%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.79854. Missing scores are unknown.","source_id":"sr-5488f3b109b9d417d0648edca794f196"}],"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-59557c9d6b271a21e1a0c5472f86fa91","url":"https://github.com/advisories/GHSA-25mq-v84q-4j7r","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-25mq-v84q-4j7r","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:40.011Z"},{"id":"sr-d34ae8d3cfc52d1130e77d5a122fc249","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-31090","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2022-31090","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T23:14:26.524Z"},{"id":"sr-5488f3b109b9d417d0648edca794f196","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-2022-31090","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-59557c9d6b271a21e1a0c5472f86fa91"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\n`Authorization` headers on requests are sensitive information. When using our Curl handler, it is possible to use the `CURLOPT_HTTPAUTH` option to specify an `Authorization` header. On making a request which responds with a redirect to a URI with a different origin, if we choose to follow it, we should remove the `CURLOPT_HTTPAUTH` and `CURLOPT_USERPWD` options before continuing, stopping curl from appending the `Authorization` header to the new request. Previously, we would only consider a change in host. Now, we consider any change in host, port or scheme to be a change in origin.\n\n### Patches\n\nAffected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in Guzzle 7.4.2, where a change in host would trigger removal of the curl-added Authorization header, however this earlier fix did not cover change in scheme or change in port.\n\n### Workarounds\n\nIf you do not require or expect redirects to be followed, one should simply disable redirects all together. Alternatively, one can specify to use the Guzzle stream handler backend, r","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.5.8"]},{"certainty":"source_listed","source_ids":["sr-59557c9d6b271a21e1a0c5472f86fa91"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\n`Authorization` headers on requests are sensitive information. When using our Curl handler, it is possible to use the `CURLOPT_HTTPAUTH` option to specify an `Authorization` header. On making a request which responds with a redirect to a URI with a different origin, if we choose to follow it, we should remove the `CURLOPT_HTTPAUTH` and `CURLOPT_USERPWD` options before continuing, stopping curl from appending the `Authorization` header to the new request. Previously, we would only consider a change in host. Now, we consider any change in host, port or scheme to be a change in origin.\n\n### Patches\n\nAffected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in Guzzle 7.4.2, where a change in host would trigger removal of the curl-added Authorization header, however this earlier fix did not cover change in scheme or change in port.\n\n### Workarounds\n\nIf you do not require or expect redirects to be followed, one should simply disable redirects all together. Alternatively, one can specify to use the Guzzle stream handler backend, r","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.5"]}],"null_published_at":"2026-11-07T22:29:23.446Z","source_updated_at":"2024-02-16T08:21:48.242Z","source_disclosed_at":"2022-06-21T16:57:10.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:41:40.011Z"},{"id":"NVI-00004131","kind":"vulnerability","title":"CURLOPT_HTTPAUTH option not cleared on change of origin","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-25mq-v84q-4j7r","CVE-2022-31090"],"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.8 for guzzlehttp/guzzle. Confirm the publisher’s latest guidance.","source_ids":["sr-59557c9d6b271a21e1a0c5472f86fa91"],"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.5 for guzzlehttp/guzzle. Confirm the publisher’s latest guidance.","source_ids":["sr-59557c9d6b271a21e1a0c5472f86fa91"],"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":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-5488f3b109b9d417d0648edca794f196"],"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":"1.916%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.79854. Missing scores are unknown.","source_id":"sr-5488f3b109b9d417d0648edca794f196"}],"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-59557c9d6b271a21e1a0c5472f86fa91","url":"https://github.com/advisories/GHSA-25mq-v84q-4j7r","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-25mq-v84q-4j7r","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:40.011Z"},{"id":"sr-5488f3b109b9d417d0648edca794f196","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-2022-31090","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-59557c9d6b271a21e1a0c5472f86fa91"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\n`Authorization` headers on requests are sensitive information. When using our Curl handler, it is possible to use the `CURLOPT_HTTPAUTH` option to specify an `Authorization` header. On making a request which responds with a redirect to a URI with a different origin, if we choose to follow it, we should remove the `CURLOPT_HTTPAUTH` and `CURLOPT_USERPWD` options before continuing, stopping curl from appending the `Authorization` header to the new request. Previously, we would only consider a change in host. Now, we consider any change in host, port or scheme to be a change in origin.\n\n### Patches\n\nAffected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in Guzzle 7.4.2, where a change in host would trigger removal of the curl-added Authorization header, however this earlier fix did not cover change in scheme or change in port.\n\n### Workarounds\n\nIf you do not require or expect redirects to be followed, one should simply disable redirects all together. Alternatively, one can specify to use the Guzzle stream handler backend, r","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.5.8"]},{"certainty":"source_listed","source_ids":["sr-59557c9d6b271a21e1a0c5472f86fa91"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\n`Authorization` headers on requests are sensitive information. When using our Curl handler, it is possible to use the `CURLOPT_HTTPAUTH` option to specify an `Authorization` header. On making a request which responds with a redirect to a URI with a different origin, if we choose to follow it, we should remove the `CURLOPT_HTTPAUTH` and `CURLOPT_USERPWD` options before continuing, stopping curl from appending the `Authorization` header to the new request. Previously, we would only consider a change in host. Now, we consider any change in host, port or scheme to be a change in origin.\n\n### Patches\n\nAffected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in Guzzle 7.4.2, where a change in host would trigger removal of the curl-added Authorization header, however this earlier fix did not cover change in scheme or change in port.\n\n### Workarounds\n\nIf you do not require or expect redirects to be followed, one should simply disable redirects all together. Alternatively, one can specify to use the Guzzle stream handler backend, r","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.5"]}],"null_published_at":"2026-11-01T01:04:04.845Z","source_updated_at":"2024-02-16T08:21:48.242Z","source_disclosed_at":"2022-06-21T16:57:10.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-31T21:41:40.011Z"},{"id":"NVI-00004131","kind":"vulnerability","title":"CURLOPT_HTTPAUTH option not cleared on change of origin","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-25mq-v84q-4j7r","CVE-2022-31090"],"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.8 for guzzlehttp/guzzle. Confirm the publisher’s latest guidance.","source_ids":["sr-59557c9d6b271a21e1a0c5472f86fa91"],"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.5 for guzzlehttp/guzzle. Confirm the publisher’s latest guidance.","source_ids":["sr-59557c9d6b271a21e1a0c5472f86fa91"],"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-59557c9d6b271a21e1a0c5472f86fa91","url":"https://github.com/advisories/GHSA-25mq-v84q-4j7r","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-25mq-v84q-4j7r","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:40.011Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-59557c9d6b271a21e1a0c5472f86fa91"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\n`Authorization` headers on requests are sensitive information. When using our Curl handler, it is possible to use the `CURLOPT_HTTPAUTH` option to specify an `Authorization` header. On making a request which responds with a redirect to a URI with a different origin, if we choose to follow it, we should remove the `CURLOPT_HTTPAUTH` and `CURLOPT_USERPWD` options before continuing, stopping curl from appending the `Authorization` header to the new request. Previously, we would only consider a change in host. Now, we consider any change in host, port or scheme to be a change in origin.\n\n### Patches\n\nAffected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in Guzzle 7.4.2, where a change in host would trigger removal of the curl-added Authorization header, however this earlier fix did not cover change in scheme or change in port.\n\n### Workarounds\n\nIf you do not require or expect redirects to be followed, one should simply disable redirects all together. Alternatively, one can specify to use the Guzzle stream handler backend, r","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.5.8"]},{"certainty":"source_listed","source_ids":["sr-59557c9d6b271a21e1a0c5472f86fa91"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\n`Authorization` headers on requests are sensitive information. When using our Curl handler, it is possible to use the `CURLOPT_HTTPAUTH` option to specify an `Authorization` header. On making a request which responds with a redirect to a URI with a different origin, if we choose to follow it, we should remove the `CURLOPT_HTTPAUTH` and `CURLOPT_USERPWD` options before continuing, stopping curl from appending the `Authorization` header to the new request. Previously, we would only consider a change in host. Now, we consider any change in host, port or scheme to be a change in origin.\n\n### Patches\n\nAffected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in Guzzle 7.4.2, where a change in host would trigger removal of the curl-added Authorization header, however this earlier fix did not cover change in scheme or change in port.\n\n### Workarounds\n\nIf you do not require or expect redirects to be followed, one should simply disable redirects all together. Alternatively, one can specify to use the Guzzle stream handler backend, r","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.5"]}],"null_published_at":"2026-10-31T22:12:52.629Z","source_updated_at":"2024-02-16T08:21:48.242Z","source_disclosed_at":"2022-06-21T16:57:10.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:41:40.011Z"}],"next_cursor":null,"snapshot_revision":"42594"}