{"items":[{"id":"NVI-00003358","kind":"vulnerability","title":"Symfony: Unbounded Recursion in the YAML Inline Lexer Lets a Single Document Crash the Process","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-2v3c-qxhr-7vpv","CVE-2026-109413"],"plain_summary":"GitHub lists this reviewed advisory for symfony/symfony, symfony/symfony, symfony/symfony, symfony/symfony, symfony/yaml. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1128188cd7ce9bbcea3c6aab168b642f"],"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},{"summary":"The original advisory lists fixed boundaries 5.4.54 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.45 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.18 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.1.6 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.54 for symfony/yaml. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.45 for symfony/yaml. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.18 for symfony/yaml. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.1.6 for symfony/yaml. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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":[{"kind":"CVSS","as_of":"2026-10-16T16:00:33.533Z","value":"8.7 HIGH (4.0)","meaning":"596c5446-0ce5-4ba2-aa66-48b3b757a647 severity; no combined Null risk score.","source_id":"sr-d8bb4570c3f93144eb78f121aa60470e"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.395%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.33765. Missing scores are unknown.","source_id":"sr-1128188cd7ce9bbcea3c6aab168b642f"}],"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-d11f4122c63661698f6203fbd7533e4a","url":"https://github.com/advisories/GHSA-2v3c-qxhr-7vpv","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-2v3c-qxhr-7vpv","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:36.327Z"},{"id":"sr-3ba9f2663394407586963abaf084c315","url":"https://github.com/advisories/GHSA-2v3c-qxhr-7vpv","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-2v3c-qxhr-7vpv","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.645Z"},{"id":"sr-d8bb4570c3f93144eb78f121aa60470e","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-109413","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-109413","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T01:40:38.141Z"},{"id":"sr-1128188cd7ce9bbcea3c6aab168b642f","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-109413","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.840Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 2.0.0, < 5.4.54"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 6.0.0, < 6.4.45"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 7.0.0, < 7.4.18"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 8.0.0, < 8.1.6"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 2.0.0, < 5.4.54"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 6.0.0, < 6.4.45"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 7.0.0, < 7.4.18"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 8.0.0, < 8.1.6"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 5.4.54"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.45"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.18"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.1.6"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 5.4.54"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.45"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.18"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.1.6"]}],"null_published_at":"2026-11-07T22:29:23.455Z","source_updated_at":"2026-10-27T19:01:52.000Z","source_disclosed_at":"2026-10-27T19:01:50.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:49.645Z"},{"id":"NVI-00003358","kind":"vulnerability","title":"Symfony: Unbounded Recursion in the YAML Inline Lexer Lets a Single Document Crash the Process","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-2v3c-qxhr-7vpv","CVE-2026-109413"],"plain_summary":"GitHub lists this reviewed advisory for symfony/symfony, symfony/symfony, symfony/symfony, symfony/symfony, symfony/yaml. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1128188cd7ce9bbcea3c6aab168b642f"],"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},{"summary":"The original advisory lists fixed boundaries 5.4.54 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.45 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.18 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.1.6 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.54 for symfony/yaml. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.45 for symfony/yaml. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.18 for symfony/yaml. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.1.6 for symfony/yaml. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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":[{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.395%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.33765. Missing scores are unknown.","source_id":"sr-1128188cd7ce9bbcea3c6aab168b642f"}],"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-d11f4122c63661698f6203fbd7533e4a","url":"https://github.com/advisories/GHSA-2v3c-qxhr-7vpv","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-2v3c-qxhr-7vpv","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:36.327Z"},{"id":"sr-3ba9f2663394407586963abaf084c315","url":"https://github.com/advisories/GHSA-2v3c-qxhr-7vpv","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-2v3c-qxhr-7vpv","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.645Z"},{"id":"sr-1128188cd7ce9bbcea3c6aab168b642f","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-109413","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.840Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 2.0.0, < 5.4.54"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 6.0.0, < 6.4.45"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 7.0.0, < 7.4.18"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 8.0.0, < 8.1.6"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 2.0.0, < 5.4.54"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 6.0.0, < 6.4.45"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 7.0.0, < 7.4.18"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 8.0.0, < 8.1.6"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 5.4.54"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.45"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.18"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.1.6"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 5.4.54"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.45"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.18"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.1.6"]}],"null_published_at":"2026-11-04T10:04:47.606Z","source_updated_at":"2026-10-27T19:01:52.000Z","source_disclosed_at":"2026-10-27T19:01:50.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:49.645Z"},{"id":"NVI-00003358","kind":"vulnerability","title":"Symfony: Unbounded Recursion in the YAML Inline Lexer Lets a Single Document Crash the Process","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-2v3c-qxhr-7vpv","CVE-2026-109413"],"plain_summary":"GitHub lists this reviewed advisory for symfony/symfony, symfony/symfony, symfony/symfony, symfony/symfony, symfony/yaml. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"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},{"summary":"The original advisory lists fixed boundaries 5.4.54 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.45 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.18 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.1.6 for symfony/symfony. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.54 for symfony/yaml. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.45 for symfony/yaml. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.18 for symfony/yaml. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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.1.6 for symfony/yaml. Confirm the publisher’s latest guidance.","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"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-d11f4122c63661698f6203fbd7533e4a","url":"https://github.com/advisories/GHSA-2v3c-qxhr-7vpv","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-2v3c-qxhr-7vpv","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:36.327Z"},{"id":"sr-3ba9f2663394407586963abaf084c315","url":"https://github.com/advisories/GHSA-2v3c-qxhr-7vpv","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-2v3c-qxhr-7vpv","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.645Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 2.0.0, < 5.4.54"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 6.0.0, < 6.4.45"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 7.0.0, < 7.4.18"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 8.0.0, < 8.1.6"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 2.0.0, < 5.4.54"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 6.0.0, < 6.4.45"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 7.0.0, < 7.4.18"]},{"certainty":"source_listed","source_ids":["sr-d11f4122c63661698f6203fbd7533e4a"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":[">= 8.0.0, < 8.1.6"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 5.4.54"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.45"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.18"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/symfony","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.1.6"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 2.0.0; fixed 5.4.54"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.4.45"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 7.0.0; fixed 7.4.18"]},{"certainty":"source_listed","source_ids":["sr-3ba9f2663394407586963abaf084c315"],"technology":"symfony/yaml","known_exclusions":[],"conditions_summary":"### Description\n\n`Yaml\\Parser::lexInlineStructure()` recursed through `lexInlineMapping()` and `lexInlineSequence()` for every `{` and `[` of an inline collection, without entering the nesting level that the rest of the parser bounds with `maxNestingLevel`. A document made of deeply nested inline collections, such as `[[[[...]]]]`, exhausted the stack while it was being lexed: depending on the PHP version and its stack settings, the process crashed or the request ended with a fatal error.\n\nAny code parsing untrusted YAML is affected. That includes `#[MapRequestPayload]` when the Yaml component is installed and the endpoint does not restrict `acceptFormat`: a single unauthenticated request with a YAML content type is enough.\n\n### Resolution\n\nThe inline lexer now enters and leaves the same nesting level as the rest of the parser, so nested inline collections are bounded by `maxNestingLevel`, and the parser raises a `ParseException` beyond it.\n\nThe patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).\n\n### Credits\n\nWe would like to thank Nicolas Greka","public_affected_ranges":["ECOSYSTEM: introduced 8.0.0; fixed 8.1.6"]}],"null_published_at":"2026-10-31T22:13:31.287Z","source_updated_at":"2026-10-27T19:01:52.000Z","source_disclosed_at":"2026-10-27T19:01:50.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:49.645Z"}],"next_cursor":null,"snapshot_revision":"42594"}