Advisory

GHSA-2v3c-qxhr-7vpv

Also known as: CVE-2026-109413

Summary

Symfony: Unbounded Recursion in the YAML Inline Lexer Lets a Single Document Crash the Process

Details

Description

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.

Any 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.

Resolution

The 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.

The patches for this issue are available here for branch 5.4 (and forward-ported to 6.4, 7.4, 8.1 and 8.2).

Credits

We would like to thank Nicolas Grekas for reporting the issue and providing the fix.

References

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-10-27 19:01 UTC
Modified
2026-10-27 19:15 UTC

Affected packages and fixes

symfony/symfony

Packagist · All systems

Affected

  • introduced 2.0.0, fixed 5.4.54 (ecosystem)

Fixed versions

5.4.54

Fix

The export has no generic command for this ecosystem.

symfony/symfony

Packagist · All systems

Affected

  • introduced 6.0.0, fixed 6.4.45 (ecosystem)

Fixed versions

6.4.45

Fix

The export has no generic command for this ecosystem.

symfony/symfony

Packagist · All systems

Affected

  • introduced 7.0.0, fixed 7.4.18 (ecosystem)

Fixed versions

7.4.18

Fix

The export has no generic command for this ecosystem.

symfony/symfony

Packagist · All systems

Affected

  • introduced 8.0.0, fixed 8.1.6 (ecosystem)

Fixed versions

8.1.6

Fix

The export has no generic command for this ecosystem.

symfony/yaml

Packagist · All systems

Affected

  • introduced 2.0.0, fixed 5.4.54 (ecosystem)

Fixed versions

5.4.54

Fix

The export has no generic command for this ecosystem.

symfony/yaml

Packagist · All systems

Affected

  • introduced 6.0.0, fixed 6.4.45 (ecosystem)

Fixed versions

6.4.45

Fix

The export has no generic command for this ecosystem.

symfony/yaml

Packagist · All systems

Affected

  • introduced 7.0.0, fixed 7.4.18 (ecosystem)

Fixed versions

7.4.18

Fix

The export has no generic command for this ecosystem.

symfony/yaml

Packagist · All systems

Affected

  • introduced 8.0.0, fixed 8.1.6 (ecosystem)

Fixed versions

8.1.6

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences