{"items":[{"id":"NVI-00002849","kind":"vulnerability","title":"Symfony has a UrlGenerator Route-Requirement Bypass via Unanchored Regex Alternation → Off-Site //host URL Injection","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-72xp-p242-47p9","CVE-2026-45065"],"plain_summary":"OSV carries this publisher advisory for symfony/routing, symfony/routing, symfony/routing, symfony/routing, symfony/symfony. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.4.52 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.40 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.52 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.40 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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-06917d1caae0545448ed1fe8eba5b5cc"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.348%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.28455. Missing scores are unknown.","source_id":"sr-06917d1caae0545448ed1fe8eba5b5cc"}],"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-28f4334824025fd15a9a28b1cbcbcaf3","url":"https://github.com/advisories/GHSA-72xp-p242-47p9","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-72xp-p242-47p9","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.943Z"},{"id":"sr-06917d1caae0545448ed1fe8eba5b5cc","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-45065","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.854Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.52"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.40"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.12"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.0.12"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.52"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.40"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.12"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.0.12"]}],"null_published_at":"2026-11-03T17:49:15.012Z","source_updated_at":"2026-09-10T03:50:45.964Z","source_disclosed_at":"2026-05-27T16:55:16.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:59.943Z"},{"id":"NVI-00002849","kind":"vulnerability","title":"Symfony has a UrlGenerator Route-Requirement Bypass via Unanchored Regex Alternation → Off-Site //host URL Injection","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-72xp-p242-47p9","CVE-2026-45065"],"plain_summary":"OSV carries this publisher advisory for symfony/routing, symfony/routing, symfony/routing, symfony/routing, symfony/symfony. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.4.52 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.40 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.52 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.40 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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-0133915caaf1ae90178275fa41f7bdc9"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.348%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.28464. Missing scores are unknown.","source_id":"sr-0133915caaf1ae90178275fa41f7bdc9"}],"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-28f4334824025fd15a9a28b1cbcbcaf3","url":"https://github.com/advisories/GHSA-72xp-p242-47p9","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-72xp-p242-47p9","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.943Z"},{"id":"sr-0133915caaf1ae90178275fa41f7bdc9","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-45065","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.279Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.52"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.40"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.12"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.0.12"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.52"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.40"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.12"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.0.12"]}],"null_published_at":"2026-11-02T20:21:07.734Z","source_updated_at":"2026-09-10T03:50:45.964Z","source_disclosed_at":"2026-05-27T16:55:16.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:59.943Z"},{"id":"NVI-00002849","kind":"vulnerability","title":"Symfony has a UrlGenerator Route-Requirement Bypass via Unanchored Regex Alternation → Off-Site //host URL Injection","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-72xp-p242-47p9","CVE-2026-45065"],"plain_summary":"OSV carries this publisher advisory for symfony/routing, symfony/routing, symfony/routing, symfony/routing, symfony/symfony. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.4.52 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.40 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.52 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.40 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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-4b3f7da253e7a03e070620ad5056f83d"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.348%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.28467. Missing scores are unknown.","source_id":"sr-4b3f7da253e7a03e070620ad5056f83d"}],"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-28f4334824025fd15a9a28b1cbcbcaf3","url":"https://github.com/advisories/GHSA-72xp-p242-47p9","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-72xp-p242-47p9","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.943Z"},{"id":"sr-4b3f7da253e7a03e070620ad5056f83d","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-45065","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.52"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.40"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.12"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.0.12"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.52"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.40"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.12"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.0.12"]}],"null_published_at":"2026-10-31T23:18:17.268Z","source_updated_at":"2026-09-10T03:50:45.964Z","source_disclosed_at":"2026-05-27T16:55:16.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:59.943Z"},{"id":"NVI-00002849","kind":"vulnerability","title":"Symfony has a UrlGenerator Route-Requirement Bypass via Unanchored Regex Alternation → Off-Site //host URL Injection","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-72xp-p242-47p9","CVE-2026-45065"],"plain_summary":"OSV carries this publisher advisory for symfony/routing, symfony/routing, symfony/routing, symfony/routing, symfony/symfony. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 5.4.52 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.40 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/routing. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.52 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.40 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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.12 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"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-28f4334824025fd15a9a28b1cbcbcaf3","url":"https://github.com/advisories/GHSA-72xp-p242-47p9","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-72xp-p242-47p9","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.943Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.52"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.40"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.12"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/routing","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.0.12"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 5.4.52"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.40"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.12"]},{"certainty":"source_listed","source_ids":["sr-28f4334824025fd15a9a28b1cbcbcaf3"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\nSymfony routes can declare a requirements regex per path parameter, e.g. a route `/{_locale}/blog` with `requirements: { _locale: 'en|fr|de' }`. The Twig `path()` / `url()` helpers (backed by `UrlGenerator`) validate supplied parameter values against that regex before building the URL.\n\nUrlGenerator constructs the validation pattern as `'#^'.$req.'$#'`, where `$req` is the raw requirement string. For a requirement expressed as an alternation, e.g. `_locale: 'ar|bg|...|vi|...|zh_CN'` (very common), `^` and `$` anchor only the first and last alternatives, so any middle alternative matches as an unanchored substring. A value like `/evil.com` satisfies the requirement (because it contains `vi`), and the generated path becomes `//evil.com/...`: a protocol-relative URL the browser navigates off-site.\n\n### Resolution\n\nThe `UrlGenerator` class now wraps the requirement in a non-capturing group so the `^` and `$` anchors apply to the whole alternation.\n\nThe patch for this issue is available here for branch 5.4.\n\n### Credits\n\nSymfony would like to thank Claude Mythos Preview (via Project Gl","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.0.12"]}],"null_published_at":"2026-10-31T22:12:38.454Z","source_updated_at":"2026-09-10T03:50:45.964Z","source_disclosed_at":"2026-05-27T16:55:16.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:41:59.943Z"}],"next_cursor":null,"snapshot_revision":"42594"}