{"items":[{"id":"NVI-00004095","kind":"vulnerability","title":"Symfony: Security Firewall Bypass via failure_forward Subrequest: Unauthenticated Access to access_control-Protected GET Routes","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-6h46-9jf5-q59x","CVE-2026-48489"],"plain_summary":"OSV carries this publisher advisory for symfony/security-http, symfony/symfony, symfony/security-http, symfony/security-http, symfony/security-http. 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.4.53 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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.4.53 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 6.4.41 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 7.4.13 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 8.0.13 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 6.4.41 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 7.4.13 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 8.0.13 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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-2b58ae31d23bc052e29a148bcc90cf6e"],"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-07-16T15:16:31.970Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-3336bb2e75e08dedcc025d91071dc8a1"},{"kind":"CVSS","as_of":"2026-07-16T15:16:31.970Z","value":"8.7 HIGH (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-3336bb2e75e08dedcc025d91071dc8a1"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.596%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.48507. Missing scores are unknown.","source_id":"sr-2b58ae31d23bc052e29a148bcc90cf6e"}],"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-57c24dae0e3abfddc20e2c4fe87f423a","url":"https://github.com/advisories/GHSA-6h46-9jf5-q59x","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-6h46-9jf5-q59x","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.936Z"},{"id":"sr-3336bb2e75e08dedcc025d91071dc8a1","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-48489","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-48489","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:22.913Z"},{"id":"sr-2b58ae31d23bc052e29a148bcc90cf6e","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-48489","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.855Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.53"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.53"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.41"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.13"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.0.13"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.41"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.13"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.0.13"]}],"null_published_at":"2026-11-08T19:53:38.914Z","source_updated_at":"2026-09-10T03:51:08.102Z","source_disclosed_at":"2026-06-15T17:28:20.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.936Z"},{"id":"NVI-00004095","kind":"vulnerability","title":"Symfony: Security Firewall Bypass via failure_forward Subrequest: Unauthenticated Access to access_control-Protected GET Routes","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-6h46-9jf5-q59x","CVE-2026-48489"],"plain_summary":"OSV carries this publisher advisory for symfony/security-http, symfony/symfony, symfony/security-http, symfony/security-http, symfony/security-http. 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.4.53 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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.4.53 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 6.4.41 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 7.4.13 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 8.0.13 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 6.4.41 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 7.4.13 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 8.0.13 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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-3336bb2e75e08dedcc025d91071dc8a1"],"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-07-16T15:16:31.970Z","value":"7.5 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-3336bb2e75e08dedcc025d91071dc8a1"},{"kind":"CVSS","as_of":"2026-07-16T15:16:31.970Z","value":"8.7 HIGH (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-3336bb2e75e08dedcc025d91071dc8a1"}],"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-57c24dae0e3abfddc20e2c4fe87f423a","url":"https://github.com/advisories/GHSA-6h46-9jf5-q59x","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-6h46-9jf5-q59x","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.936Z"},{"id":"sr-3336bb2e75e08dedcc025d91071dc8a1","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-48489","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-48489","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:22.913Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.53"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.53"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.41"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.13"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.0.13"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.41"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.13"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.0.13"]}],"null_published_at":"2026-11-01T14:34:07.618Z","source_updated_at":"2026-09-10T03:51:08.102Z","source_disclosed_at":"2026-06-15T17:28:20.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:41:59.936Z"},{"id":"NVI-00004095","kind":"vulnerability","title":"Symfony: Security Firewall Bypass via failure_forward Subrequest: Unauthenticated Access to access_control-Protected GET Routes","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-6h46-9jf5-q59x","CVE-2026-48489"],"plain_summary":"OSV carries this publisher advisory for symfony/security-http, symfony/symfony, symfony/security-http, symfony/security-http, symfony/security-http. 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.4.53 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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.4.53 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 6.4.41 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 7.4.13 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 8.0.13 for symfony/security-http. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 6.4.41 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 7.4.13 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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 8.0.13 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"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-57c24dae0e3abfddc20e2c4fe87f423a","url":"https://github.com/advisories/GHSA-6h46-9jf5-q59x","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-6h46-9jf5-q59x","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.936Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.53"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.53"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.41"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.13"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/security-http","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.0.13"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.41"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.13"]},{"certainty":"source_listed","source_ids":["sr-57c24dae0e3abfddc20e2c4fe87f423a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nWhen a firewall is configured with `form-login` (or any authenticator using `DefaultAuthenticationFailureHandler`) and the `failure_forward: true` option, the handler reads the `_failure_path` parameter from the failing login request and uses it as the path of an internal subrequest dispatched through `HttpKernelInterface::SUB_REQUEST`.\n\nSymfony's `Firewall::onKernelRequest` listener intentionally skips subrequests under the assumption they are internally generated and trusted, which also means `AccessListener` (the listener that evaluates `access_control`) does not run. Because the attacker controls the target of the subrequest, an unauthenticated POST to the check path with `_failure_path=/admin/whatever` performs a local request forgery that executes the target controller outside the firewall perimeter and returns its response to the caller.\n\nApplications that follow Symfony's recommended best practice of protecting administrative areas with broad `access_control` rules (e.g. `^/admin` requires `ROLE_ADMIN`) and expose read-only GET endpoints under that area (data exports, internal APIs, account views) are fully exposed: any such GET route can be read by an unau","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.0.13"]}],"null_published_at":"2026-10-31T22:12:52.627Z","source_updated_at":"2026-09-10T03:51:08.102Z","source_disclosed_at":"2026-06-15T17:28:20.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.936Z"}],"next_cursor":null,"snapshot_revision":"42594"}