{"items":[{"id":"NVI-00005815","kind":"vulnerability","title":"Guzzle: Unbounded response cookies risk denial of service","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-f283-ghqc-fg79","CVE-2026-67353"],"plain_summary":"OSV carries this publisher advisory for 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 7.15.1 for guzzlehttp/guzzle. Confirm the publisher’s latest guidance.","source_ids":["sr-9dbbc6105ab674321c4f3b62b9eb5bfe"],"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-48b5ff8893ddfbeaccbf081a2538e0df"],"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.418%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.36142. Missing scores are unknown.","source_id":"sr-48b5ff8893ddfbeaccbf081a2538e0df"}],"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-9dbbc6105ab674321c4f3b62b9eb5bfe","url":"https://github.com/advisories/GHSA-f283-ghqc-fg79","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-f283-ghqc-fg79","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.706Z"},{"id":"sr-48b5ff8893ddfbeaccbf081a2538e0df","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-67353","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.384Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-9dbbc6105ab674321c4f3b62b9eb5bfe"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\nIn affected versions, Guzzle's built-in `CookieJar` accepts any number of `Set-Cookie` header fields from one response, with no limit on the size of each field. When a later request matches the stored cookies, Guzzle places every match into one generated `Cookie` header without limiting the number of cookies or the total header length.\n\nA malicious or compromised server can therefore return many large cookies, causing Guzzle to store attacker-controlled data in memory and copy it into later request headers. This can increase memory use and processing time. It can also make later requests fail when the generated header exceeds a limit in a handler, HTTP implementation, proxy, or destination server. A server on one sibling host, such as `attacker.example.com`, can also set parent-domain cookies that are later selected for another sibling, such as `service.example.com`. The denial can therefore affect a different service that uses the same jar.\n\nAn application is affected when it enables the built-in cookie support, receives an attacker-controlled response, and retains or reuses the jar. The issue affects both built-in handlers because Guzzle manages these cookies itself i","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 7.15.1"]}],"null_published_at":"2026-10-31T23:18:17.256Z","source_updated_at":"2026-09-10T03:50:51.710Z","source_disclosed_at":"2026-07-20T23:27:02.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:10.706Z"},{"id":"NVI-00005815","kind":"vulnerability","title":"Guzzle: Unbounded response cookies risk denial of service","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-f283-ghqc-fg79","CVE-2026-67353"],"plain_summary":"OSV carries this publisher advisory for 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 7.15.1 for guzzlehttp/guzzle. Confirm the publisher’s latest guidance.","source_ids":["sr-9dbbc6105ab674321c4f3b62b9eb5bfe"],"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-9dbbc6105ab674321c4f3b62b9eb5bfe","url":"https://github.com/advisories/GHSA-f283-ghqc-fg79","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-f283-ghqc-fg79","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.706Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-9dbbc6105ab674321c4f3b62b9eb5bfe"],"technology":"guzzlehttp/guzzle","known_exclusions":[],"conditions_summary":"### Impact\n\nIn affected versions, Guzzle's built-in `CookieJar` accepts any number of `Set-Cookie` header fields from one response, with no limit on the size of each field. When a later request matches the stored cookies, Guzzle places every match into one generated `Cookie` header without limiting the number of cookies or the total header length.\n\nA malicious or compromised server can therefore return many large cookies, causing Guzzle to store attacker-controlled data in memory and copy it into later request headers. This can increase memory use and processing time. It can also make later requests fail when the generated header exceeds a limit in a handler, HTTP implementation, proxy, or destination server. A server on one sibling host, such as `attacker.example.com`, can also set parent-domain cookies that are later selected for another sibling, such as `service.example.com`. The denial can therefore affect a different service that uses the same jar.\n\nAn application is affected when it enables the built-in cookie support, receives an attacker-controlled response, and retains or reuses the jar. The issue affects both built-in handlers because Guzzle manages these cookies itself i","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 7.15.1"]}],"null_published_at":"2026-10-31T22:13:05.839Z","source_updated_at":"2026-09-10T03:50:51.710Z","source_disclosed_at":"2026-07-20T23:27:02.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:10.706Z"}],"next_cursor":null,"snapshot_revision":"42594"}