{"items":[{"id":"NVI-00002817","kind":"vulnerability","title":"Prevent cache poisoning via a Response Content-Type header in Symfony","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-mcx4-f5f5-4859","CVE-2020-5255"],"plain_summary":"OSV carries this publisher advisory for symfony/http-foundation, symfony/http-foundation, symfony/symfony, symfony/symfony. 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 4.4.7 for symfony/http-foundation. Confirm the publisher’s latest guidance.","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"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 5.0.7 for symfony/http-foundation. Confirm the publisher’s latest guidance.","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"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 4.4.7 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"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 5.0.7 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"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-cc620b04effcf8805fe5aff03051b75c"],"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-17T03:21:08.493Z","value":"4 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-833c509aaabd5c9bda431497ba713576"},{"kind":"CVSS","as_of":"2026-06-17T03:21:08.493Z","value":"2.6 LOW (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-833c509aaabd5c9bda431497ba713576"},{"kind":"CVSS","as_of":"2026-06-17T03:21:08.493Z","value":"4.3 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-833c509aaabd5c9bda431497ba713576"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"1.297%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.70389. Missing scores are unknown.","source_id":"sr-cc620b04effcf8805fe5aff03051b75c"}],"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-280b023a3b9a7db5b45255001d84ff31","url":"https://github.com/advisories/GHSA-mcx4-f5f5-4859","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-mcx4-f5f5-4859","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.978Z"},{"id":"sr-833c509aaabd5c9bda431497ba713576","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-5255","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2020-5255","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T22:07:21.349Z"},{"id":"sr-cc620b04effcf8805fe5aff03051b75c","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-2020-5255","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"technology":"symfony/http-foundation","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nWhen a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.\n\nResolution\n----------\n\nSymfony does not use the `Accept` header anymore to guess the `Content-Type`.\n\nThe patch for this issue is available here for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.4.0; fixed 4.4.7"]},{"certainty":"source_listed","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"technology":"symfony/http-foundation","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nWhen a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.\n\nResolution\n----------\n\nSymfony does not use the `Accept` header anymore to guess the `Content-Type`.\n\nThe patch for this issue is available here for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.0.7"]},{"certainty":"source_listed","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nWhen a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.\n\nResolution\n----------\n\nSymfony does not use the `Accept` header anymore to guess the `Content-Type`.\n\nThe patch for this issue is available here for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.4.0; fixed 4.4.7"]},{"certainty":"source_listed","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nWhen a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.\n\nResolution\n----------\n\nSymfony does not use the `Accept` header anymore to guess the `Content-Type`.\n\nThe patch for this issue is available here for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.0.7"]}],"null_published_at":"2026-11-06T21:03:48.036Z","source_updated_at":"2026-09-10T03:48:29.528Z","source_disclosed_at":"2020-03-30T20:09: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.978Z"},{"id":"NVI-00002817","kind":"vulnerability","title":"Prevent cache poisoning via a Response Content-Type header in Symfony","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-mcx4-f5f5-4859","CVE-2020-5255"],"plain_summary":"OSV carries this publisher advisory for symfony/http-foundation, symfony/http-foundation, symfony/symfony, symfony/symfony. 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 4.4.7 for symfony/http-foundation. Confirm the publisher’s latest guidance.","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"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 5.0.7 for symfony/http-foundation. Confirm the publisher’s latest guidance.","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"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 4.4.7 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"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 5.0.7 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"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-833c509aaabd5c9bda431497ba713576"],"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-17T03:21:08.493Z","value":"4 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-833c509aaabd5c9bda431497ba713576"},{"kind":"CVSS","as_of":"2026-06-17T03:21:08.493Z","value":"2.6 LOW (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-833c509aaabd5c9bda431497ba713576"},{"kind":"CVSS","as_of":"2026-06-17T03:21:08.493Z","value":"4.3 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-833c509aaabd5c9bda431497ba713576"}],"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-280b023a3b9a7db5b45255001d84ff31","url":"https://github.com/advisories/GHSA-mcx4-f5f5-4859","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-mcx4-f5f5-4859","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.978Z"},{"id":"sr-833c509aaabd5c9bda431497ba713576","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-5255","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2020-5255","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T22:07:21.349Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"technology":"symfony/http-foundation","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nWhen a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.\n\nResolution\n----------\n\nSymfony does not use the `Accept` header anymore to guess the `Content-Type`.\n\nThe patch for this issue is available here for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.4.0; fixed 4.4.7"]},{"certainty":"source_listed","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"technology":"symfony/http-foundation","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nWhen a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.\n\nResolution\n----------\n\nSymfony does not use the `Accept` header anymore to guess the `Content-Type`.\n\nThe patch for this issue is available here for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.0.7"]},{"certainty":"source_listed","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nWhen a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.\n\nResolution\n----------\n\nSymfony does not use the `Accept` header anymore to guess the `Content-Type`.\n\nThe patch for this issue is available here for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.4.0; fixed 4.4.7"]},{"certainty":"source_listed","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nWhen a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.\n\nResolution\n----------\n\nSymfony does not use the `Accept` header anymore to guess the `Content-Type`.\n\nThe patch for this issue is available here for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.0.7"]}],"null_published_at":"2026-10-31T22:27:06.715Z","source_updated_at":"2026-09-10T03:48:29.528Z","source_disclosed_at":"2020-03-30T20:09: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.978Z"},{"id":"NVI-00002817","kind":"vulnerability","title":"Prevent cache poisoning via a Response Content-Type header in Symfony","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-mcx4-f5f5-4859","CVE-2020-5255"],"plain_summary":"OSV carries this publisher advisory for symfony/http-foundation, symfony/http-foundation, symfony/symfony, symfony/symfony. 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 4.4.7 for symfony/http-foundation. Confirm the publisher’s latest guidance.","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"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 5.0.7 for symfony/http-foundation. Confirm the publisher’s latest guidance.","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"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 4.4.7 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"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 5.0.7 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"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-280b023a3b9a7db5b45255001d84ff31","url":"https://github.com/advisories/GHSA-mcx4-f5f5-4859","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-mcx4-f5f5-4859","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.978Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"technology":"symfony/http-foundation","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nWhen a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.\n\nResolution\n----------\n\nSymfony does not use the `Accept` header anymore to guess the `Content-Type`.\n\nThe patch for this issue is available here for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.4.0; fixed 4.4.7"]},{"certainty":"source_listed","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"technology":"symfony/http-foundation","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nWhen a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.\n\nResolution\n----------\n\nSymfony does not use the `Accept` header anymore to guess the `Content-Type`.\n\nThe patch for this issue is available here for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.0.7"]},{"certainty":"source_listed","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nWhen a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.\n\nResolution\n----------\n\nSymfony does not use the `Accept` header anymore to guess the `Content-Type`.\n\nThe patch for this issue is available here for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.4.0; fixed 4.4.7"]},{"certainty":"source_listed","source_ids":["sr-280b023a3b9a7db5b45255001d84ff31"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nWhen a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.\n\nResolution\n----------\n\nSymfony does not use the `Accept` header anymore to guess the `Content-Type`.\n\nThe patch for this issue is available here for the 4.4 branch.\n\nCredits\n-------\n\nI would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.0.7"]}],"null_published_at":"2026-10-31T22:12:38.453Z","source_updated_at":"2026-09-10T03:48:29.528Z","source_disclosed_at":"2020-03-30T20:09: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.978Z"}],"next_cursor":null,"snapshot_revision":"42594"}