{"items":[{"id":"NVI-00002395","kind":"vulnerability","title":"Change in port should be considered a change in 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-q559-8m2m-g699","CVE-2022-31091"],"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-1666ab9e0ff05a22b925c94b3e65577c"],"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-1666ab9e0ff05a22b925c94b3e65577c"],"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-0ffc4f0a35aa0cd3f5ff9784d7da9b59"],"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.673Z","value":"4 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-1cee81fa7a66172f710a037812d865e4"},{"kind":"CVSS","as_of":"2026-06-17T04:44:46.673Z","value":"7.7 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-1cee81fa7a66172f710a037812d865e4"},{"kind":"CVSS","as_of":"2026-06-17T04:44:46.673Z","value":"7.7 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-1cee81fa7a66172f710a037812d865e4"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"1.565%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.753. Missing scores are unknown.","source_id":"sr-0ffc4f0a35aa0cd3f5ff9784d7da9b59"}],"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-1666ab9e0ff05a22b925c94b3e65577c","url":"https://github.com/advisories/GHSA-q559-8m2m-g699","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-q559-8m2m-g699","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.998Z"},{"id":"sr-1cee81fa7a66172f710a037812d865e4","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-31091","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2022-31091","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T23:14:26.524Z"},{"id":"sr-0ffc4f0a35aa0cd3f5ff9784d7da9b59","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-31091","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:14:50.774Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1666ab9e0ff05a22b925c94b3e65577c"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\n`Authorization` and `Cookie` headers on requests are sensitive information. On making a request which responds with a redirect to a URI with a different port, if we choose to follow it, we should remove the `Authorization` and `Cookie` headers from the request, before containing. Previously, we would only consider a change in host or scheme downgrade. 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.\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* CVE-2022-27776\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](https://php","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.5.8"]},{"certainty":"source_listed","source_ids":["sr-1666ab9e0ff05a22b925c94b3e65577c"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\n`Authorization` and `Cookie` headers on requests are sensitive information. On making a request which responds with a redirect to a URI with a different port, if we choose to follow it, we should remove the `Authorization` and `Cookie` headers from the request, before containing. Previously, we would only consider a change in host or scheme downgrade. 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.\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* CVE-2022-27776\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](https://php","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.5"]}],"null_published_at":"2026-11-04T10:04:47.601Z","source_updated_at":"2023-11-08T04:09:25.594Z","source_disclosed_at":"2022-06-21T20:07:16.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:42:30.998Z"},{"id":"NVI-00002395","kind":"vulnerability","title":"Change in port should be considered a change in origin","revision":2,"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-q559-8m2m-g699","CVE-2022-31091"],"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-1666ab9e0ff05a22b925c94b3e65577c"],"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-1666ab9e0ff05a22b925c94b3e65577c"],"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-1cee81fa7a66172f710a037812d865e4"],"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.673Z","value":"4 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-1cee81fa7a66172f710a037812d865e4"},{"kind":"CVSS","as_of":"2026-06-17T04:44:46.673Z","value":"7.7 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-1cee81fa7a66172f710a037812d865e4"},{"kind":"CVSS","as_of":"2026-06-17T04:44:46.673Z","value":"7.7 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-1cee81fa7a66172f710a037812d865e4"}],"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-1666ab9e0ff05a22b925c94b3e65577c","url":"https://github.com/advisories/GHSA-q559-8m2m-g699","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-q559-8m2m-g699","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.998Z"},{"id":"sr-1cee81fa7a66172f710a037812d865e4","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-31091","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2022-31091","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T23:14:26.524Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1666ab9e0ff05a22b925c94b3e65577c"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\n`Authorization` and `Cookie` headers on requests are sensitive information. On making a request which responds with a redirect to a URI with a different port, if we choose to follow it, we should remove the `Authorization` and `Cookie` headers from the request, before containing. Previously, we would only consider a change in host or scheme downgrade. 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.\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* CVE-2022-27776\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](https://php","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.5.8"]},{"certainty":"source_listed","source_ids":["sr-1666ab9e0ff05a22b925c94b3e65577c"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\n`Authorization` and `Cookie` headers on requests are sensitive information. On making a request which responds with a redirect to a URI with a different port, if we choose to follow it, we should remove the `Authorization` and `Cookie` headers from the request, before containing. Previously, we would only consider a change in host or scheme downgrade. 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.\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* CVE-2022-27776\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](https://php","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.5"]}],"null_published_at":"2026-11-01T01:04:01.266Z","source_updated_at":"2023-11-08T04:09:25.594Z","source_disclosed_at":"2022-06-21T20:07:16.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:42:30.998Z"},{"id":"NVI-00002395","kind":"vulnerability","title":"Change in port should be considered a change in origin","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-q559-8m2m-g699","CVE-2022-31091"],"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-1666ab9e0ff05a22b925c94b3e65577c"],"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-1666ab9e0ff05a22b925c94b3e65577c"],"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-1666ab9e0ff05a22b925c94b3e65577c","url":"https://github.com/advisories/GHSA-q559-8m2m-g699","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-q559-8m2m-g699","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.998Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1666ab9e0ff05a22b925c94b3e65577c"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\n`Authorization` and `Cookie` headers on requests are sensitive information. On making a request which responds with a redirect to a URI with a different port, if we choose to follow it, we should remove the `Authorization` and `Cookie` headers from the request, before containing. Previously, we would only consider a change in host or scheme downgrade. 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.\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* CVE-2022-27776\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](https://php","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.5.8"]},{"certainty":"source_listed","source_ids":["sr-1666ab9e0ff05a22b925c94b3e65577c"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\n`Authorization` and `Cookie` headers on requests are sensitive information. On making a request which responds with a redirect to a URI with a different port, if we choose to follow it, we should remove the `Authorization` and `Cookie` headers from the request, before containing. Previously, we would only consider a change in host or scheme downgrade. 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.\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* CVE-2022-27776\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](https://php","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.5"]}],"null_published_at":"2026-10-31T22:00:33.880Z","source_updated_at":"2023-11-08T04:09:25.594Z","source_disclosed_at":"2022-06-21T20:07:16.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:30.998Z"}],"next_cursor":null,"snapshot_revision":"42594"}