Symfony XML decoding attack vector through external entities
Priority LOW 38CWE-611Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
The XMLEncoder component of Symfony 2.0.x fails to disable external entities when parsing XML. In the Symfony2 framework the XML class may be used to deserialize objects or as part of a client/server API. By using external entities it is possible to include arbitrary files from the file system.
Why it matters now
Fix Fixed symfony/serializer (Packagist): 2.0.11
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | symfony/serializer (Packagist) | 2.0.0 to before 2.0.11 | 2.0.11 | Patch available | GHSA-j68w-pg49-f6vx |
- symfony/serializer (Packagist) Vendor— Affected 2.0.0 to before 2.0.11 Fixed in 2.0.11 Patch available GHSA-j68w-pg49-f6vx
Remediation
- Fix · GHSA-j68w-pg49-f6vx symfony/serializer (Packagist) Fixed in 2.0.11 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-j68w-pg49-f6vx
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences