{"items":[{"id":"NVI-00003862","kind":"vulnerability","title":"Prevent user enumeration using Guard or the new Authenticator-based Security","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-5pv8-ppvj-4h68","CVE-2021-21424"],"plain_summary":"OSV carries this publisher advisory for symfony/security, symfony/security-guard, symfony/security-guard, symfony/security-guard, symfony/security-core. 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 5.2.8 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.4.48 for symfony/security-guard. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.23 for symfony/security-guard. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.2.8 for symfony/security-guard. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.4.48 for symfony/security-core. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.23 for symfony/security-core. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.2.8 for symfony/security-core. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.10.7 for lexik/jwt-authentication-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.11.3 for lexik/jwt-authentication-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.29.2 for symfony/maker-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.31.1 for symfony/maker-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.2.8 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.4.49 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.24 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.4.49 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.24 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.2.9 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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-056f1901ece380643cef6cf73a5860da"],"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:35:32.947Z","value":"5 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-3ece7a32be114cd44f0bebdd28bd05bd"},{"kind":"CVSS","as_of":"2026-06-17T03:35:32.947Z","value":"5.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-3ece7a32be114cd44f0bebdd28bd05bd"},{"kind":"CVSS","as_of":"2026-06-17T03:35:32.947Z","value":"5.3 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-3ece7a32be114cd44f0bebdd28bd05bd"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"1.644%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.76466. Missing scores are unknown.","source_id":"sr-056f1901ece380643cef6cf73a5860da"}],"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-4da72345dca151664fa07da78202f75b","url":"https://github.com/advisories/GHSA-5pv8-ppvj-4h68","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-5pv8-ppvj-4h68","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.926Z"},{"id":"sr-3ece7a32be114cd44f0bebdd28bd05bd","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-21424","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2021-21424","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T22:07:35.928Z"},{"id":"sr-056f1901ece380643cef6cf73a5860da","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-2021-21424","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:42:56.080Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.2.8"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-guard","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 3.4.48"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-guard","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.4.23"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-guard","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.2.8"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-core","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 3.4.48"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-core","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.4.23"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-core","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.2.8"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"lexik/jwt-authentication-bundle","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.10.7"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"lexik/jwt-authentication-bundle","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.11.0; fixed 2.11.3"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/maker-bundle","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 1.27.0; fixed 1.29.2"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/maker-bundle","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 1.30.0; fixed 1.31.1"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.1.0; fixed 5.2.8"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 3.4.49"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.4.24"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 3.4.49"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.4.24"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.2.9"]}],"null_published_at":"2026-11-04T10:04:41.547Z","source_updated_at":"2026-09-10T03:49:04.871Z","source_disclosed_at":"2021-05-13T20:23: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:41:59.926Z"},{"id":"NVI-00003862","kind":"vulnerability","title":"Prevent user enumeration using Guard or the new Authenticator-based Security","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-5pv8-ppvj-4h68","CVE-2021-21424"],"plain_summary":"OSV carries this publisher advisory for symfony/security, symfony/security-guard, symfony/security-guard, symfony/security-guard, symfony/security-core. 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 5.2.8 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.4.48 for symfony/security-guard. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.23 for symfony/security-guard. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.2.8 for symfony/security-guard. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.4.48 for symfony/security-core. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.23 for symfony/security-core. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.2.8 for symfony/security-core. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.10.7 for lexik/jwt-authentication-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.11.3 for lexik/jwt-authentication-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.29.2 for symfony/maker-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.31.1 for symfony/maker-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.2.8 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.4.49 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.24 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.4.49 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.24 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.2.9 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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-379c9b9adc9b5df104f8283b93943818"],"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:35:32.947Z","value":"5 MEDIUM (2.0)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-3ece7a32be114cd44f0bebdd28bd05bd"},{"kind":"CVSS","as_of":"2026-06-17T03:35:32.947Z","value":"5.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-3ece7a32be114cd44f0bebdd28bd05bd"},{"kind":"CVSS","as_of":"2026-06-17T03:35:32.947Z","value":"5.3 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-3ece7a32be114cd44f0bebdd28bd05bd"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"1.644%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.76441. Missing scores are unknown.","source_id":"sr-379c9b9adc9b5df104f8283b93943818"}],"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-4da72345dca151664fa07da78202f75b","url":"https://github.com/advisories/GHSA-5pv8-ppvj-4h68","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-5pv8-ppvj-4h68","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.926Z"},{"id":"sr-3ece7a32be114cd44f0bebdd28bd05bd","url":"https://nvd.nist.gov/vuln/detail/CVE-2021-21424","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2021-21424","publisher":"NIST National Vulnerability Database","observed_at":"2026-10-31T22:07:35.928Z"},{"id":"sr-379c9b9adc9b5df104f8283b93943818","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-2021-21424","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.2.8"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-guard","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 3.4.48"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-guard","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.4.23"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-guard","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.2.8"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-core","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 3.4.48"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-core","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.4.23"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-core","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.2.8"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"lexik/jwt-authentication-bundle","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.10.7"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"lexik/jwt-authentication-bundle","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.11.0; fixed 2.11.3"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/maker-bundle","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 1.27.0; fixed 1.29.2"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/maker-bundle","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 1.30.0; fixed 1.31.1"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.1.0; fixed 5.2.8"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 3.4.49"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.4.24"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 3.4.49"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.4.24"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.2.9"]}],"null_published_at":"2026-10-31T22:27:15.291Z","source_updated_at":"2026-09-10T03:49:04.871Z","source_disclosed_at":"2021-05-13T20:23: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:41:59.926Z"},{"id":"NVI-00003862","kind":"vulnerability","title":"Prevent user enumeration using Guard or the new Authenticator-based Security","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-5pv8-ppvj-4h68","CVE-2021-21424"],"plain_summary":"OSV carries this publisher advisory for symfony/security, symfony/security-guard, symfony/security-guard, symfony/security-guard, symfony/security-core. 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 5.2.8 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.4.48 for symfony/security-guard. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.23 for symfony/security-guard. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.2.8 for symfony/security-guard. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.4.48 for symfony/security-core. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.23 for symfony/security-core. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.2.8 for symfony/security-core. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.10.7 for lexik/jwt-authentication-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.11.3 for lexik/jwt-authentication-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.29.2 for symfony/maker-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.31.1 for symfony/maker-bundle. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.2.8 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.4.49 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.24 for symfony/security. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.4.49 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.24 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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.2.9 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"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-4da72345dca151664fa07da78202f75b","url":"https://github.com/advisories/GHSA-5pv8-ppvj-4h68","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-5pv8-ppvj-4h68","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.926Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.2.8"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-guard","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 3.4.48"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-guard","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.4.23"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-guard","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.2.8"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-core","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 3.4.48"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-core","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.4.23"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-core","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.2.8"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"lexik/jwt-authentication-bundle","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 2.10.7"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"lexik/jwt-authentication-bundle","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.11.0; fixed 2.11.3"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/maker-bundle","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 1.27.0; fixed 1.29.2"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/maker-bundle","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 1.30.0; fixed 1.31.1"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.1.0; fixed 5.2.8"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 3.4.49"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/security","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.4.24"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 2.8.0; fixed 3.4.49"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.4.24"]},{"certainty":"source_listed","source_ids":["sr-4da72345dca151664fa07da78202f75b"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"Description\n-----------\n\nThe ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.\n\nResolution\n----------\n\nWe now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.\n\nThe patch for this issue is available here for branch 3.4.\n\nCredits\n-------\n\nI would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.","public_affected_ranges":["ECOSYSTEM: introduced 5.0.0; fixed 5.2.9"]}],"null_published_at":"2026-10-31T22:12:52.601Z","source_updated_at":"2026-09-10T03:49:04.871Z","source_disclosed_at":"2021-05-13T20:23: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:41:59.926Z"}],"next_cursor":null,"snapshot_revision":"42594"}