CVE-2026-118515 (GCVE-0-2026-118515)
Vulnerability from cvelistv5 – Published: 2026-11-06 16:17 – Updated: 2026-11-06 16:17
VLAI
EPSS
VEX
Title
Symfony: The Serializer Builds UploadedFile Objects From Request Data, Letting a Client Point an Upload at Any Server File
Summary
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.
Severity
CWE
- CWE-73 - External control of file name or path
Assigner
Checkmarx
CNA
References
3 references
| URL | Tags |
|---|---|
| https://github.com/symfony/symfony/security/advis… | third-party-advisory |
| https://github.com/symfony/symfony/commit/72ece5b… | patch |
| https://github.com/symfony/symfony/commit/c459104… | patch |
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| sensiolabs | symfony |
Affected:
0 , < 5.4.56
(git)
Affected: 6.0.0 , < 6.4.50 (git) Affected: 7.0.0 , < 7.4.23 (git) Affected: 8.0.0 , < 8.1.11 (git) cpe:2.3:a:sensiolabs:symfony:*:*:*:*:*:*:*:* cpe:2.3:a:sensiolabs:symfony:*:*:*:*:*:*:*:* cpe:2.3:a:sensiolabs:symfony:*:*:*:*:*:*:*:* cpe:2.3:a:sensiolabs:symfony:*:*:*:*:*:*:*:* |
{
"containers": {
"cna": {
"affected": [
{
"collectionURL": "https://packagist.org/packages/symfony/serializer",
"defaultStatus": "unaffected",
"modules": [
"Symfony\\Component\\Serializer\\Normalizer\\DataUriNormalizer::denormalize()"
],
"packageName": "symfony/serializer",
"product": "symfony",
"repo": "https://github.com/symfony/serializer",
"vendor": "sensiolabs",
"versions": [
{
"lessThan": "5.4.56",
"status": "affected",
"version": "0",
"versionType": "git"
},
{
"lessThan": "6.4.50",
"status": "affected",
"version": "6.0.0",
"versionType": "git"
},
{
"lessThan": "7.4.23",
"status": "affected",
"version": "7.0.0",
"versionType": "git"
},
{
"lessThan": "8.1.11",
"status": "affected",
"version": "8.0.0",
"versionType": "git"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:sensiolabs:symfony:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.4.56",
"versionStartIncluding": "0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:sensiolabs:symfony:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.4.50",
"versionStartIncluding": "6.0.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:sensiolabs:symfony:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4.23",
"versionStartIncluding": "7.0.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:sensiolabs:symfony:*:*:*:*:*:*:*:*",
"versionEndExcluding": "8.1.11",
"versionStartIncluding": "8.0.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "OR"
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Oliver Wenzel"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Nicolas Grekas"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cdiv\u003eThe Symfony Serializer component\u0026nbsp;\u003ccode\u003eDataUriNormalizer\u003c/code\u003e\u0026nbsp;handles only the exact types\u0026nbsp;\u003ccode\u003eSplFileInfo\u003c/code\u003e\u003cspan\u003e, \u003c/span\u003e\u003ccode\u003eSplFileObject\u003c/code\u003e\u003cspan\u003e, and \u003c/span\u003e\u003ccode\u003eFile\u003c/code\u003e\u003cspan\u003e, so for a property typed with a subclass such as \u003c/span\u003e\u003ccode\u003eUploadedFile\u003c/code\u003e\u003cspan\u003e, \u003c/span\u003e\u003ccode\u003eObjectNormalizer\u003c/code\u003e\u003cspan\u003e 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.\u003c/span\u003e\u003c/div\u003e\u003cdiv\u003eA request body such as\u0026nbsp;\u003ccode\u003e{\"image\": {\"path\": \"/path/to/project/.env.local\", \"originalName\": \"a.png\", \"test\": true}}\u003c/code\u003e\u0026nbsp;makes the application handle any file on the server as an upload, without the file being sent. With\u0026nbsp;\u003ccode\u003etest: true\u003c/code\u003e,\u0026nbsp;\u003ccode\u003eUploadedFile::isValid()\u003c/code\u003e\u0026nbsp;skips\u0026nbsp;\u003ccode\u003eis_uploaded_file()\u003c/code\u003e\u0026nbsp;and\u0026nbsp;\u003ccode\u003emove()\u003c/code\u003e\u0026nbsp;falls back to\u0026nbsp;\u003ccode\u003erename()\u003c/code\u003e.\u0026nbsp;\u003ccode\u003eAssert\\File\u003c/code\u003e\u0026nbsp;does not prevent this because it validates\u0026nbsp;the file at the attacker-chosen path, which exists on the server.\u003cbr\u003e\u003cdiv\u003eAny code that deserializes untrusted data into a type that holds such a property is affected. That includes\u0026nbsp;\u003ccode\u003e#[MapRequestPayload]\u003c/code\u003e\u0026nbsp;on a DTO with an\u0026nbsp;\u003ccode\u003eUploadedFile\u003c/code\u003e\u0026nbsp;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\u0026nbsp;\u003ccode\u003emove()\u003c/code\u003e\u0026nbsp;is called, and reveal whether a path exists.\u003c/div\u003e\u003cdiv\u003eA serializer built without\u0026nbsp;\u003ccode\u003eDataUriNormalizer\u003c/code\u003e\u0026nbsp;ahead of the object normalizer is not protected by the fix; the serializer configured by\u0026nbsp;\u003ccode\u003eFrameworkBundle\u003c/code\u003e\u0026nbsp;is.\u003c/div\u003e\u003c/div\u003e"
}
],
"value": "The Symfony Serializer component\u00a0DataUriNormalizer\u00a0handles only the exact types\u00a0SplFileInfo, 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.\n\nA request body such as\u00a0{\"image\": {\"path\": \"/path/to/project/.env.local\", \"originalName\": \"a.png\", \"test\": true}}\u00a0makes the application handle any file on the server as an upload, without the file being sent. With\u00a0test: true,\u00a0UploadedFile::isValid()\u00a0skips\u00a0is_uploaded_file()\u00a0and\u00a0move()\u00a0falls back to\u00a0rename().\u00a0Assert\\File\u00a0does not prevent this because it validates\u00a0the file at the attacker-chosen path, which exists on the server.\nAny code that deserializes untrusted data into a type that holds such a property is affected. That includes\u00a0#[MapRequestPayload]\u00a0on a DTO with an\u00a0UploadedFile\u00a0property, 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\u00a0move()\u00a0is called, and reveal whether a path exists.\n\nA serializer built without\u00a0DataUriNormalizer\u00a0ahead of the object normalizer is not protected by the fix; the serializer configured by\u00a0FrameworkBundle\u00a0is."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 8.4,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:H/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "LOW",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-73",
"description": "CWE-73 External control of file name or path",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-06T16:17:01.487Z",
"orgId": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
"shortName": "Checkmarx"
},
"references": [
{
"tags": [
"third-party-advisory"
],
"url": "https://github.com/symfony/symfony/security/advisories/GHSA-h38r-xrmh-cwhr"
},
{
"tags": [
"patch"
],
"url": "https://github.com/symfony/symfony/commit/72ece5bb3084e8233325166357f85c8c0650ee86"
},
{
"tags": [
"patch"
],
"url": "https://github.com/symfony/symfony/commit/c459104eb18ebda31e112c5490970da3f30bd668"
}
],
"source": {
"advisory": "GHSA-h38r-xrmh-cwhr",
"discovery": "UNKNOWN"
},
"title": "Symfony: The Serializer Builds UploadedFile Objects From Request Data, Letting a Client Point an Upload at Any Server File",
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
"assignerShortName": "Checkmarx",
"cveId": "CVE-2026-118515",
"datePublished": "2026-11-06T16:17:01.487Z",
"dateReserved": "2026-10-28T14:33:36.992Z",
"dateUpdated": "2026-11-06T16:17:01.487Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Loading…
Loading…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.