{"items":[{"id":"NVI-00003900","kind":"vulnerability","title":"Symfony CSRF Vulnerability","revision":4,"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-92x6-h2gr-8gxq","CVE-2017-16653"],"plain_summary":"OSV carries this publisher advisory for symfony/security-csrf, symfony/security-csrf, symfony/security-csrf, symfony/security-csrf, symfony/security. 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 2.7.38 for symfony/security-csrf. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 2.8.31 for symfony/security-csrf. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.2.14 for symfony/security-csrf. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.3.13 for symfony/security-csrf. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 2.7.38 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 2.8.31 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.2.14 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.3.13 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 2.7.38 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 2.8.31 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.2.14 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.3.13 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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-4020005f520c50b318d7656f02ad2dc9"],"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-17T01:09:37.673Z","value":"4.3 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-87ab76892b51532a42031e4998e1c8da"},{"kind":"CVSS","as_of":"2026-06-17T01:09:37.673Z","value":"5.9 MEDIUM (3.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-87ab76892b51532a42031e4998e1c8da"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"1.486%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.7403. Missing scores are unknown.","source_id":"sr-4020005f520c50b318d7656f02ad2dc9"}],"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-4f10a401eea7d6c4b461954354b86886","url":"https://github.com/advisories/GHSA-92x6-h2gr-8gxq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-92x6-h2gr-8gxq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.678Z"},{"id":"sr-87ab76892b51532a42031e4998e1c8da","url":"https://nvd.nist.gov/vuln/detail/CVE-2017-16653","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2017-16653","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T21:56:48.322Z"},{"id":"sr-4020005f520c50b318d7656f02ad2dc9","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-2017-16653","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:27:48.610Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security-csrf","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.7.0; fixed 2.7.38"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security-csrf","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.8.31"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security-csrf","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.2.14"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security-csrf","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.13"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.7.0; fixed 2.7.38"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.8.31"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.2.14"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.13"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.7.0; fixed 2.7.38"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.8.31"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.2.14"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.13"]}],"null_published_at":"2026-11-08T19:53:48.772Z","source_updated_at":"2024-02-16T08:15:55.037Z","source_disclosed_at":"2022-05-13T01:44:08.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.678Z"},{"id":"NVI-00003900","kind":"vulnerability","title":"Symfony CSRF Vulnerability","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-92x6-h2gr-8gxq","CVE-2017-16653"],"plain_summary":"OSV carries this publisher advisory for symfony/security-csrf, symfony/security-csrf, symfony/security-csrf, symfony/security-csrf, symfony/security. 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 2.7.38 for symfony/security-csrf. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 2.8.31 for symfony/security-csrf. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.2.14 for symfony/security-csrf. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.3.13 for symfony/security-csrf. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 2.7.38 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 2.8.31 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.2.14 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.3.13 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 2.7.38 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 2.8.31 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.2.14 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.3.13 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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-45447cd1094e289c83d47f178c1ce7e4"],"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-17T01:09:37.673Z","value":"4.3 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-87ab76892b51532a42031e4998e1c8da"},{"kind":"CVSS","as_of":"2026-06-17T01:09:37.673Z","value":"5.9 MEDIUM (3.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-87ab76892b51532a42031e4998e1c8da"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"1.486%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.7403. Missing scores are unknown.","source_id":"sr-45447cd1094e289c83d47f178c1ce7e4"}],"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-4f10a401eea7d6c4b461954354b86886","url":"https://github.com/advisories/GHSA-92x6-h2gr-8gxq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-92x6-h2gr-8gxq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.678Z"},{"id":"sr-87ab76892b51532a42031e4998e1c8da","url":"https://nvd.nist.gov/vuln/detail/CVE-2017-16653","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2017-16653","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T21:56:48.322Z"},{"id":"sr-45447cd1094e289c83d47f178c1ce7e4","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-2017-16653","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security-csrf","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.7.0; fixed 2.7.38"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security-csrf","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.8.31"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security-csrf","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.2.14"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security-csrf","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.13"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.7.0; fixed 2.7.38"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.8.31"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.2.14"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.13"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.7.0; fixed 2.7.38"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.8.31"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.2.14"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.13"]}],"null_published_at":"2026-10-31T23:18:17.231Z","source_updated_at":"2024-02-16T08:15:55.037Z","source_disclosed_at":"2022-05-13T01:44:08.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.678Z"},{"id":"NVI-00003900","kind":"vulnerability","title":"Symfony CSRF Vulnerability","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-92x6-h2gr-8gxq","CVE-2017-16653"],"plain_summary":"OSV carries this publisher advisory for symfony/security-csrf, symfony/security-csrf, symfony/security-csrf, symfony/security-csrf, symfony/security. 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 2.7.38 for symfony/security-csrf. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 2.8.31 for symfony/security-csrf. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.2.14 for symfony/security-csrf. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.3.13 for symfony/security-csrf. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 2.7.38 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 2.8.31 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.2.14 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.3.13 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 2.7.38 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 2.8.31 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.2.14 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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 3.3.13 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"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-87ab76892b51532a42031e4998e1c8da"],"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-17T01:09:37.673Z","value":"4.3 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-87ab76892b51532a42031e4998e1c8da"},{"kind":"CVSS","as_of":"2026-06-17T01:09:37.673Z","value":"5.9 MEDIUM (3.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-87ab76892b51532a42031e4998e1c8da"}],"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-4f10a401eea7d6c4b461954354b86886","url":"https://github.com/advisories/GHSA-92x6-h2gr-8gxq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-92x6-h2gr-8gxq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.678Z"},{"id":"sr-87ab76892b51532a42031e4998e1c8da","url":"https://nvd.nist.gov/vuln/detail/CVE-2017-16653","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2017-16653","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T21:56:48.322Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security-csrf","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.7.0; fixed 2.7.38"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security-csrf","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.8.31"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security-csrf","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.2.14"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security-csrf","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.13"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.7.0; fixed 2.7.38"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.8.31"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.2.14"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.13"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.7.0; fixed 2.7.38"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 2.8.31"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.2.14"]},{"certainty":"source_listed","source_ids":["sr-4f10a401eea7d6c4b461954354b86886"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0; fixed 3.3.13"]}],"null_published_at":"2026-10-31T22:13:35.659Z","source_updated_at":"2024-02-16T08:15:55.037Z","source_disclosed_at":"2022-05-13T01:44:08.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:10.678Z"}],"next_cursor":null,"snapshot_revision":"42594"}