Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-118515

The Symfony Serializer componentDataUriNormalizerhandles only the exac ...

Overview

Published
6 Nov 2026
Modified
11 Nov 2026
High CVE
2 Registry packages
1 OS packages
2 Linux distributions
Yes Fix available
CVSS score High, no score

Description

The Symfony Serializer component DataUriNormalizer handles only the exact types SplFileInfo, SplFileObject, and File, so for a property typed with a subclass such as UploadedFile, ObjectNormalizer instantiates the object through its constructor from attacker-controlled data, including the file path. This allows an arbitrary file on the server to be treated as an uploaded file 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 request body such as {"image": {"path": "/path/to/project/.env.local", "originalName": "a.png", "test": true}} makes the application handle any file on the server as an upload, without the file being sent. With test: true, UploadedFile::isValid() skips is_uploaded_file() and move() falls back to rename(). Assert\File does not prevent this because it validates the file at the attacker-chosen path, which exists on the server.
Any code that deserializes untrusted data into a type that holds such a property is affected. That includes #[MapRequestPayload] on a DTO with an UploadedFile property, which is how uploads are mapped in Symfony 8.1; a single unauthenticated request with a JSON or form body is enough. Depending on what the application does with the upload, this can expose any file readable by PHP (for instance, when uploads are stored and served back), move any such file when move() is called, and reveal whether a path exists.

A serializer built without DataUriNormalizer ahead of the object normalizer is not protected by the fix; the serializer configured by FrameworkBundle is.

Source: OX vulnerability database

Severity

HIGH

No CVSS vector in the source. Severity comes from the advisory.

Weakness: CWE-73

Affected packages · 2

Packages affected by CVE-2026-118515
EcosystemPackageVulnerableFixed in
Composer (PHP) symfony/serializer >=7.2.0, <7.3.0>=6.1.0, <6.2.0>=6.3.0, <6.4.0>=7.4.0, <7.4.23>=8.1.0, <8.1.11+15 more No fix yet
Composer (PHP) symfony/symfony >=4.0.0, <5.0.0>=5.0.0, <5.1.0>=7.3.0, <7.4.0>=7.4.0, <7.4.23>=6.2.0, <6.3.0+15 more No fix yet

Open a package to see all its vulnerabilities.

Operating systems · 5 fixes

debian 4 releases · 1 package

affected 2 fixed 2
symfony
debian fixes for CVE-2026-118515
ReleasePackageFixed in
11 symfony affected
12 symfony affected
13 symfony 6.4.50+dfsg-0+deb13u1
14 symfony 7.4.23+dfsg-1

echo 1 release · 1 package

fixed 1
symfony
echo fixes for CVE-2026-118515
ReleasePackageFixed in
symfony 6.4.50+dfsg-0+deb13u1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.