Skip to main content
VulnerabilityPublished Updated

CVE-2026-122053: The Symfony Serializer component ObjectNormalizer treats any attribute name containing

Affects symfonySource GCVE Database

0
Compare
Authoritative record:CVE-2026-122053· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium.

Data as of 18 Nov 2026, 15:20 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Sources agree

CVSS scores by source
CNA (Checkmarx)CVSS 4.06.9
CISA-ADPCVSS 3.16.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10symfonypkg:deb/ubuntu/symfony?arch=source&distro=stonkingOther threatsAffected
  • 7.4.7+dfsg-1ubuntu1 – 7.4.16+dfsg-1ubuntu2
6 affected builds
Fixed in–
Ubuntu 26.04 LTSsymfonypkg:deb/ubuntu/symfony?arch=source&distro=resoluteOther threatsAffected
  • 6.4.24+dfsg-1 – 7.4.7+dfsg-1ubuntu1
4 affected builds
Fixed in–
Ubuntu Pro 24.04 LTSsymfonypkg:deb/ubuntu/symfony?arch=source&distro=esm-apps/nobleOther threatsAffected
  • 5.4.23+dfsg-1ubuntu1 – 6.4.5+dfsg-3ubuntu3+esm1
5 affected builds
Fixed in–
Ubuntu Pro 22.04 LTSsymfonypkg:deb/ubuntu/symfony?arch=source&distro=esm-apps/jammyOther threatsAffected
  • =5.2.6+dfsg-1ubuntu7
  • =5.4.4+dfsg-1ubuntu8
  • =5.4.4+dfsg-1ubuntu8+esm1
Fixed in–
Ubuntu Pro 20.04 LTSsymfonypkg:deb/ubuntu/symfony?arch=source&distro=esm-apps/focalOther threatsAffected
  • 4.3.4+dfsg-1ubuntu1 – 4.3.8+dfsg-1ubuntu1+esm2
4 affected builds
Fixed in–
Ubuntu Pro 18.04 LTSsymfonypkg:deb/ubuntu/symfony?arch=source&distro=esm-apps/bionicOther threatsAffected
  • 2.8.7+dfsg-1.3ubuntu1 – 3.4.6+dfsg-1ubuntu0.1+esm2
6 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The Symfony Serializer component ObjectNormalizer treats any attribute name containing . (and, from Symfony 6.4, [) as a writable property path, allowing untrusted input to modify properties of nested objects and bypass their #[Ignore] metadata attribute in Symfony versions 5.4.41 prior to 5.4.56, 6.4.9 prior to 6.4.50, 7.0.9 prior to 7.1.0, 7.1.2 prior to 7.4.23, and 8.x prior to 8.1.11. ObjectNormalizer::isAllowedAttribute() accepts such names, and setAttributeValue() hands the name straight to PropertyAccessor::setValue(), which parses it as a property path and traverses into the nested object. A payload key such as customer.admin writes to $order->customer->admin. The #[Ignore] metadata attribute is only consulted when the nested object is denormalized in its own right, never when it is reached through a path. #[Groups] restrictions are not bypassed: the path is only accepted when no groups are passed in the context, and then groups restrict nothing. When the root class carries neither #[Ignore] nor #[Groups], no allowlist applies and every key of the payload is let through. Because PropertyAccessor also resolves a path segment against public methods, a segment matching a public method name invokes that method with the attacker’s value.Applications that bind untrusted input to objects are affected, including controllers using #[MapRequestPayload] or #[MapQueryString], whose default normalizer is ObjectNormalizer. With OBJECT_TO_POPULATE, as used for partial updates, the traversal reaches an already hydrated entity graph, and the modified field may be persisted. The fix accepts a property path only when the class metadata declares an attribute of that exact name. Declared paths keep working unchanged, and a path in the payload with no matching declaration is ignored.

References

Community reviews

Loading reviews…