{"items":[{"id":"NVI-00002162","kind":"vulnerability","title":"Insecure header validation in slim/psr7","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-q2qj-628g-vhfw","CVE-2023-30536"],"plain_summary":"OSV carries this publisher advisory for slim/psr7, slim/psr7, slim/psr7. 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 1.6.1 for slim/psr7. Confirm the publisher’s latest guidance.","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"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 1.5.1 for slim/psr7. Confirm the publisher’s latest guidance.","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"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 1.4.1 for slim/psr7. Confirm the publisher’s latest guidance.","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"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-3f6e7636ee3e8e1670e218d53a88bbf3"],"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-17T05:54:58.160Z","value":"6.5 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-10e9ae0f2fb83a91a839b121989f727b"},{"kind":"CVSS","as_of":"2026-06-17T05:54:58.160Z","value":"6.5 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-10e9ae0f2fb83a91a839b121989f727b"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.743%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.54754. Missing scores are unknown.","source_id":"sr-3f6e7636ee3e8e1670e218d53a88bbf3"}],"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-0df7a8255f37f3f0e53f13f5adc8f3bf","url":"https://github.com/advisories/GHSA-q2qj-628g-vhfw","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-q2qj-628g-vhfw","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.997Z"},{"id":"sr-10e9ae0f2fb83a91a839b121989f727b","url":"https://nvd.nist.gov/vuln/detail/CVE-2023-30536","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2023-30536","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:58:36.867Z"},{"id":"sr-3f6e7636ee3e8e1670e218d53a88bbf3","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-2023-30536","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"technology":"slim/psr7","known_exclusions":[],"conditions_summary":"### Impact\n\nAn attacker could sneak in a newline (`\\n`) into both the header names and values. While the specification states that `\\r\\n\\r\\n` is used to terminate the header list, many servers in the wild will also accept `\\n\\n`. An attacker that is able to control the header names that are passed to Slilm-Psr7 would be able to intentionally craft invalid messages, possibly causing application errors or invalid HTTP requests being sent out with an PSR-18 HTTP client. The latter might present a denial of service vector if a remote service’s web application firewall bans the application due to the receipt of malformed requests.\n\n### Patches\n\nThe issue is patched in 1.6.1, 1.5.1, and 1.4.1.\n\n### Workarounds\n\nIn Slim-Psr7 prior to 1.6.1, 1.5.1, and 1.4.1, validate HTTP header keys and/or values, and if using user-supplied values, filter them to strip off leading or trailing newline characters before calling withHeader().\n\n### Acknowledgments\n\nWe are very grateful to and thank Graham Campbell for reporting and working with us on this issue.\n\n### References\n\n* Guzzle: CVE-2023-29197, with advisory GHSA-wxmh-65f7-jcvw\n* Laminas Diactoros: CVE-2023-2","public_affected_ranges":["ECOSYSTEM: introduced 1.6; fixed 1.6.1"]},{"certainty":"source_listed","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"technology":"slim/psr7","known_exclusions":[],"conditions_summary":"### Impact\n\nAn attacker could sneak in a newline (`\\n`) into both the header names and values. While the specification states that `\\r\\n\\r\\n` is used to terminate the header list, many servers in the wild will also accept `\\n\\n`. An attacker that is able to control the header names that are passed to Slilm-Psr7 would be able to intentionally craft invalid messages, possibly causing application errors or invalid HTTP requests being sent out with an PSR-18 HTTP client. The latter might present a denial of service vector if a remote service’s web application firewall bans the application due to the receipt of malformed requests.\n\n### Patches\n\nThe issue is patched in 1.6.1, 1.5.1, and 1.4.1.\n\n### Workarounds\n\nIn Slim-Psr7 prior to 1.6.1, 1.5.1, and 1.4.1, validate HTTP header keys and/or values, and if using user-supplied values, filter them to strip off leading or trailing newline characters before calling withHeader().\n\n### Acknowledgments\n\nWe are very grateful to and thank Graham Campbell for reporting and working with us on this issue.\n\n### References\n\n* Guzzle: CVE-2023-29197, with advisory GHSA-wxmh-65f7-jcvw\n* Laminas Diactoros: CVE-2023-2","public_affected_ranges":["ECOSYSTEM: introduced 1.5; fixed 1.5.1"]},{"certainty":"source_listed","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"technology":"slim/psr7","known_exclusions":[],"conditions_summary":"### Impact\n\nAn attacker could sneak in a newline (`\\n`) into both the header names and values. While the specification states that `\\r\\n\\r\\n` is used to terminate the header list, many servers in the wild will also accept `\\n\\n`. An attacker that is able to control the header names that are passed to Slilm-Psr7 would be able to intentionally craft invalid messages, possibly causing application errors or invalid HTTP requests being sent out with an PSR-18 HTTP client. The latter might present a denial of service vector if a remote service’s web application firewall bans the application due to the receipt of malformed requests.\n\n### Patches\n\nThe issue is patched in 1.6.1, 1.5.1, and 1.4.1.\n\n### Workarounds\n\nIn Slim-Psr7 prior to 1.6.1, 1.5.1, and 1.4.1, validate HTTP header keys and/or values, and if using user-supplied values, filter them to strip off leading or trailing newline characters before calling withHeader().\n\n### Acknowledgments\n\nWe are very grateful to and thank Graham Campbell for reporting and working with us on this issue.\n\n### References\n\n* Guzzle: CVE-2023-29197, with advisory GHSA-wxmh-65f7-jcvw\n* Laminas Diactoros: CVE-2023-2","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-11-01T01:04:01.259Z","source_updated_at":"2026-09-10T03:50:01.161Z","source_disclosed_at":"2023-04-18T22:20:42.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.997Z"},{"id":"NVI-00002162","kind":"vulnerability","title":"Insecure header validation in slim/psr7","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-q2qj-628g-vhfw","CVE-2023-30536"],"plain_summary":"OSV carries this publisher advisory for slim/psr7, slim/psr7, slim/psr7. 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 1.6.1 for slim/psr7. Confirm the publisher’s latest guidance.","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"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 1.5.1 for slim/psr7. Confirm the publisher’s latest guidance.","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"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 1.4.1 for slim/psr7. Confirm the publisher’s latest guidance.","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"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-3f6e7636ee3e8e1670e218d53a88bbf3"],"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.743%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.54754. Missing scores are unknown.","source_id":"sr-3f6e7636ee3e8e1670e218d53a88bbf3"}],"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-0df7a8255f37f3f0e53f13f5adc8f3bf","url":"https://github.com/advisories/GHSA-q2qj-628g-vhfw","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-q2qj-628g-vhfw","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.997Z"},{"id":"sr-3f6e7636ee3e8e1670e218d53a88bbf3","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-2023-30536","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"technology":"slim/psr7","known_exclusions":[],"conditions_summary":"### Impact\n\nAn attacker could sneak in a newline (`\\n`) into both the header names and values. While the specification states that `\\r\\n\\r\\n` is used to terminate the header list, many servers in the wild will also accept `\\n\\n`. An attacker that is able to control the header names that are passed to Slilm-Psr7 would be able to intentionally craft invalid messages, possibly causing application errors or invalid HTTP requests being sent out with an PSR-18 HTTP client. The latter might present a denial of service vector if a remote service’s web application firewall bans the application due to the receipt of malformed requests.\n\n### Patches\n\nThe issue is patched in 1.6.1, 1.5.1, and 1.4.1.\n\n### Workarounds\n\nIn Slim-Psr7 prior to 1.6.1, 1.5.1, and 1.4.1, validate HTTP header keys and/or values, and if using user-supplied values, filter them to strip off leading or trailing newline characters before calling withHeader().\n\n### Acknowledgments\n\nWe are very grateful to and thank Graham Campbell for reporting and working with us on this issue.\n\n### References\n\n* Guzzle: CVE-2023-29197, with advisory GHSA-wxmh-65f7-jcvw\n* Laminas Diactoros: CVE-2023-2","public_affected_ranges":["ECOSYSTEM: introduced 1.6; fixed 1.6.1"]},{"certainty":"source_listed","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"technology":"slim/psr7","known_exclusions":[],"conditions_summary":"### Impact\n\nAn attacker could sneak in a newline (`\\n`) into both the header names and values. While the specification states that `\\r\\n\\r\\n` is used to terminate the header list, many servers in the wild will also accept `\\n\\n`. An attacker that is able to control the header names that are passed to Slilm-Psr7 would be able to intentionally craft invalid messages, possibly causing application errors or invalid HTTP requests being sent out with an PSR-18 HTTP client. The latter might present a denial of service vector if a remote service’s web application firewall bans the application due to the receipt of malformed requests.\n\n### Patches\n\nThe issue is patched in 1.6.1, 1.5.1, and 1.4.1.\n\n### Workarounds\n\nIn Slim-Psr7 prior to 1.6.1, 1.5.1, and 1.4.1, validate HTTP header keys and/or values, and if using user-supplied values, filter them to strip off leading or trailing newline characters before calling withHeader().\n\n### Acknowledgments\n\nWe are very grateful to and thank Graham Campbell for reporting and working with us on this issue.\n\n### References\n\n* Guzzle: CVE-2023-29197, with advisory GHSA-wxmh-65f7-jcvw\n* Laminas Diactoros: CVE-2023-2","public_affected_ranges":["ECOSYSTEM: introduced 1.5; fixed 1.5.1"]},{"certainty":"source_listed","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"technology":"slim/psr7","known_exclusions":[],"conditions_summary":"### Impact\n\nAn attacker could sneak in a newline (`\\n`) into both the header names and values. While the specification states that `\\r\\n\\r\\n` is used to terminate the header list, many servers in the wild will also accept `\\n\\n`. An attacker that is able to control the header names that are passed to Slilm-Psr7 would be able to intentionally craft invalid messages, possibly causing application errors or invalid HTTP requests being sent out with an PSR-18 HTTP client. The latter might present a denial of service vector if a remote service’s web application firewall bans the application due to the receipt of malformed requests.\n\n### Patches\n\nThe issue is patched in 1.6.1, 1.5.1, and 1.4.1.\n\n### Workarounds\n\nIn Slim-Psr7 prior to 1.6.1, 1.5.1, and 1.4.1, validate HTTP header keys and/or values, and if using user-supplied values, filter them to strip off leading or trailing newline characters before calling withHeader().\n\n### Acknowledgments\n\nWe are very grateful to and thank Graham Campbell for reporting and working with us on this issue.\n\n### References\n\n* Guzzle: CVE-2023-29197, with advisory GHSA-wxmh-65f7-jcvw\n* Laminas Diactoros: CVE-2023-2","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-10-31T23:18:17.201Z","source_updated_at":"2026-09-10T03:50:01.161Z","source_disclosed_at":"2023-04-18T22:20:42.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.997Z"},{"id":"NVI-00002162","kind":"vulnerability","title":"Insecure header validation in slim/psr7","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-q2qj-628g-vhfw","CVE-2023-30536"],"plain_summary":"OSV carries this publisher advisory for slim/psr7, slim/psr7, slim/psr7. 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 1.6.1 for slim/psr7. Confirm the publisher’s latest guidance.","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"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 1.5.1 for slim/psr7. Confirm the publisher’s latest guidance.","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"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 1.4.1 for slim/psr7. Confirm the publisher’s latest guidance.","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"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-0df7a8255f37f3f0e53f13f5adc8f3bf","url":"https://github.com/advisories/GHSA-q2qj-628g-vhfw","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-q2qj-628g-vhfw","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.997Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"technology":"slim/psr7","known_exclusions":[],"conditions_summary":"### Impact\n\nAn attacker could sneak in a newline (`\\n`) into both the header names and values. While the specification states that `\\r\\n\\r\\n` is used to terminate the header list, many servers in the wild will also accept `\\n\\n`. An attacker that is able to control the header names that are passed to Slilm-Psr7 would be able to intentionally craft invalid messages, possibly causing application errors or invalid HTTP requests being sent out with an PSR-18 HTTP client. The latter might present a denial of service vector if a remote service’s web application firewall bans the application due to the receipt of malformed requests.\n\n### Patches\n\nThe issue is patched in 1.6.1, 1.5.1, and 1.4.1.\n\n### Workarounds\n\nIn Slim-Psr7 prior to 1.6.1, 1.5.1, and 1.4.1, validate HTTP header keys and/or values, and if using user-supplied values, filter them to strip off leading or trailing newline characters before calling withHeader().\n\n### Acknowledgments\n\nWe are very grateful to and thank Graham Campbell for reporting and working with us on this issue.\n\n### References\n\n* Guzzle: CVE-2023-29197, with advisory GHSA-wxmh-65f7-jcvw\n* Laminas Diactoros: CVE-2023-2","public_affected_ranges":["ECOSYSTEM: introduced 1.6; fixed 1.6.1"]},{"certainty":"source_listed","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"technology":"slim/psr7","known_exclusions":[],"conditions_summary":"### Impact\n\nAn attacker could sneak in a newline (`\\n`) into both the header names and values. While the specification states that `\\r\\n\\r\\n` is used to terminate the header list, many servers in the wild will also accept `\\n\\n`. An attacker that is able to control the header names that are passed to Slilm-Psr7 would be able to intentionally craft invalid messages, possibly causing application errors or invalid HTTP requests being sent out with an PSR-18 HTTP client. The latter might present a denial of service vector if a remote service’s web application firewall bans the application due to the receipt of malformed requests.\n\n### Patches\n\nThe issue is patched in 1.6.1, 1.5.1, and 1.4.1.\n\n### Workarounds\n\nIn Slim-Psr7 prior to 1.6.1, 1.5.1, and 1.4.1, validate HTTP header keys and/or values, and if using user-supplied values, filter them to strip off leading or trailing newline characters before calling withHeader().\n\n### Acknowledgments\n\nWe are very grateful to and thank Graham Campbell for reporting and working with us on this issue.\n\n### References\n\n* Guzzle: CVE-2023-29197, with advisory GHSA-wxmh-65f7-jcvw\n* Laminas Diactoros: CVE-2023-2","public_affected_ranges":["ECOSYSTEM: introduced 1.5; fixed 1.5.1"]},{"certainty":"source_listed","source_ids":["sr-0df7a8255f37f3f0e53f13f5adc8f3bf"],"technology":"slim/psr7","known_exclusions":[],"conditions_summary":"### Impact\n\nAn attacker could sneak in a newline (`\\n`) into both the header names and values. While the specification states that `\\r\\n\\r\\n` is used to terminate the header list, many servers in the wild will also accept `\\n\\n`. An attacker that is able to control the header names that are passed to Slilm-Psr7 would be able to intentionally craft invalid messages, possibly causing application errors or invalid HTTP requests being sent out with an PSR-18 HTTP client. The latter might present a denial of service vector if a remote service’s web application firewall bans the application due to the receipt of malformed requests.\n\n### Patches\n\nThe issue is patched in 1.6.1, 1.5.1, and 1.4.1.\n\n### Workarounds\n\nIn Slim-Psr7 prior to 1.6.1, 1.5.1, and 1.4.1, validate HTTP header keys and/or values, and if using user-supplied values, filter them to strip off leading or trailing newline characters before calling withHeader().\n\n### Acknowledgments\n\nWe are very grateful to and thank Graham Campbell for reporting and working with us on this issue.\n\n### References\n\n* Guzzle: CVE-2023-29197, with advisory GHSA-wxmh-65f7-jcvw\n* Laminas Diactoros: CVE-2023-2","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 1.4.1"]}],"null_published_at":"2026-10-31T21:54:04.899Z","source_updated_at":"2026-09-10T03:50:01.161Z","source_disclosed_at":"2023-04-18T22:20:42.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.997Z"}],"next_cursor":null,"snapshot_revision":"42594"}