Skepra / Web recovery & resilience

Symfony YAML: check the loaded parser and request formats

If your PHP API or import worker parses YAML supplied by other systems or users, check which copy of Symfony it actually loads. That tells you who owns the update. The formats your clients rely on determine what must pass before rollout.

Request a Recovery Review

Which versions and workloads should be checked?

On 4 November 2026, Symfony disclosed CVE-2026-123792. Certain YAML inputs can occupy a PHP process long enough to disrupt availability. For both symfony/yaml and symfony/symfony, the maintainer lists versions below 5.4.56, 6.x below 6.4.50, 7.x below 7.4.23 and 8.x below 8.1.11 as affected.

The first fixed versions in those ranges are 5.4.56, 6.4.50, 7.4.23 and 8.1.11. Review routes, uploads and background jobs that pass externally supplied YAML to the parser.

Identify the copy the service loads

Ask the application owner to check the defining file of the Symfony YAML class in an authorized staging process after normal application startup. Record the release or image and the package revision for the web process and import worker separately. If the class comes from the application's Composer dependencies, verify the installed version in that build.

If it comes from Debian's php-symfony-yaml package, check the installed distribution revision. For Debian 13 trixie, DSA-6617-1 lists 6.4.50+dfsg-0+deb13u1 as the fixed symfony source-package revision. A host package upgrade alone does not establish which code an application build or container loads.

Check the request formats clients depend on

In Symfony 6.4, MapRequestPayload accepts YAML only if the application registers a YAML request format. Starting with 7.4, affected releases could accept YAML when the component was installed and the route did not restrict accepted formats. The fix on the newer branches requires YAML or CSV to be explicitly listed in acceptFormat for MapRequestPayload to decode them.

In staging, send a normal JSON request and check its expected response. Use harmless fixtures to verify that each documented YAML or CSV input still works and that formats outside the route's contract are rejected as expected. If a separate worker parses YAML imports, run a representative test import through that worker as well.

Agree who owns the update and signs it off

Record the loaded package or build, the externally supplied inputs in scope, the tests that must pass and the owner who accepts the result. If a required format fails in staging, hold rollout and review the route configuration with the application owner. Skepra checked this advisory against public sources on 10 November 2026.

The staging checks are a proposed procedure. Recheck the vendor advisory and the distribution package status before scheduling work.