GHSA-pxj9-jh84-vhm5: Symfony: DataUriNormalizer Opens Data URIs With a Non-Lowercase Scheme as Local Files, Letting a Client Read Any Server File

Published Nov 6, 2026
·
Updated

The Symfony Serializer component DataUriNormalizer::denormalize() matches the data: scheme with a case-sensitive regular expression, allowing a value with an uppercase scheme, such as DATA:,/../../../etc/passwd, to bypass it, resulting in Arbitrary Local File Read through Path Traversal in Symfony versions prior to 5.4.56, 6.x prior to 6.4.50, 7.x prior to 7.4.23, and 8.x prior to 8.1.11.

A value whose scheme is not lowercase data: are treated as a local file path and opened instead of being decoded as inline data, so the resulting File, \SplFileInfo, or \SplFileObject points at a file on the server, which the application then handles as the uploaded content.

Any endpoint that deserializes untrusted input into one of these types is affected. FrameworkBundle registers DataUriNormalizer ahead of ObjectNormalizer by default. A single request with a crafted DATA: value is enough to read arbitrary local files that the application can access, with no authentication needed if the endpoint is public.

Affected Software

1 affected component
Symfony Serializer<5.4.56, >=6.0.0<6.4.50, >=7.0.0<7.4.23, >=8.0.0<8.1.11

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 5.4.56
  2. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 6.4.50
  3. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 7.4.23
  4. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 8.1.11

Event History

Nov 6, 2026
CVE Published
via OSV·04:08 PM
Data Sourced
via OSV·04:08 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which applications are exposed to this issue?

Applications are affected if an endpoint deserializes untrusted input into a File, SplFileInfo, or SplFileObject. FrameworkBundle registers DataUriNormalizer ahead of ObjectNormalizer by default, so applications using that default normalizer ordering can be exposed.

2

What does an attacker need to exploit it?

An attacker needs to submit a crafted value using a non-lowercase data scheme, such as a DATA: value containing path traversal, to a vulnerable deserialization endpoint. A single request is sufficient, and authentication is not required when the endpoint is public.

3

What is the impact if exploitation succeeds?

The crafted value is treated as a local file path rather than inline data, causing the resulting file object to point to a server-side file. The application may then handle that file as uploaded content, allowing reads of files accessible to the application process.

4

How can I determine whether an endpoint is affected?

Review endpoints that accept untrusted serialized input and determine whether they denormalize values into File, SplFileInfo, or SplFileObject. Also check whether the application uses a Symfony release earlier than 5.4.56, 6.4.50, 7.4.23, or 8.1.11.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203