{"id":"CVE-2026-122053","aliases":["DEBIAN-CVE-2026-122053","EUVD-2026-118360","GHSA-hqp2-7rr8-hf26","UBUNTU-CVE-2026-122053"],"status":"published","title":"Symfony: ObjectNormalizer Dotted-Key Property-Path Traversal Bypasses #[Ignore] on Nested Objects","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.\nObjectNormalizer::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-\u003ecustomer-\u003eadmin. 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.\n\nThe 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.","severity":{"version":"4.0","score":6.9,"vector":"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","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00327,"percentile":0.2616,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-915"],"published":"2026-11-06T16:46:46Z","modified":"2026-11-10T02:50:13Z","fixes":[{"ecosystem":"Debian:13","package":"symfony","fixed_in":["6.4.50+dfsg-0+deb13u1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"symfony","fixed_in":["7.4.23+dfsg-1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"symfony","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.23+dfsg-1","5.4.23+dfsg-1+deb12u1","5.4.23+dfsg-1+deb12u2","5.4.23+dfsg-1+deb12u3","5.4.23+dfsg-1+deb12u4","5.4.23+dfsg-1+deb12u5","5.4.24+dfsg-1","5.4.25+dfsg-1","5.4.27+dfsg-1","5.4.28+dfsg-1","5.4.29+dfsg-1","5.4.30+dfsg-1","5.4.31+dfsg-1","5.4.31+dfsg-2","5.4.32+dfsg-1","5.4.33+dfsg-1","5.4.34+dfsg-1","5.4.34+dfsg-2","5.4.35+dfsg-1","5.4.35+dfsg-2","5.4.35+dfsg-3","5.4.52+dfsg-0+deb12u1","5.4.53+dfsg-0+deb12u1","6.3.0+dfsg-1","6.3.0~rc1+dfsg-1","6.3.0~rc2+dfsg-1","6.3.1+dfsg-1","6.3.3+dfsg-1","6.3.4+dfsg-1","6.3.5+dfsg-1","6.3.6+dfsg-1","6.3.7+dfsg-1","6.4.0+dfsg-1","6.4.0~beta2+dfsg-1","6.4.0~beta3+dfsg-1","6.4.0~rc1+dfsg-1","6.4.0~rc2+dfsg-1","6.4.1+dfsg-1","6.4.10+dfsg-1","6.4.11+dfsg-1","6.4.12+dfsg-1","6.4.13+dfsg-1","6.4.14+dfsg-1","6.4.15+dfsg-1","6.4.16+dfsg-1","6.4.16+dfsg-2","6.4.17+dfsg-1","6.4.17+dfsg-2","6.4.17+dfsg-3","6.4.17+dfsg-4","6.4.17+dfsg-5","6.4.17+dfsg-6","6.4.18+dfsg-1","6.4.19+dfsg-1","6.4.19+dfsg-2","6.4.2+dfsg-1","6.4.20+dfsg-1","6.4.20+dfsg-2","6.4.21+dfsg-1","6.4.21+dfsg-2","6.4.24+dfsg-1","6.4.25+dfsg-1","6.4.3+dfsg-1","6.4.4+dfsg-1","6.4.4+dfsg-2","6.4.4+dfsg-3","6.4.4+dfsg-4","6.4.5+dfsg-1","6.4.5+dfsg-2","6.4.5+dfsg-3","6.4.5+dfsg-4","6.4.6+dfsg-1","6.4.7+dfsg-1","6.4.9+dfsg-1","7.0.4+dfsg-1","7.0.5+dfsg-1","7.0.6+dfsg-1","7.0.7+dfsg-1","7.1.0~beta1+dfsg-1","7.1.0~rc1+dfsg-1","7.1.2+dfsg-1","7.1.3+dfsg-1","7.1.4+dfsg-1","7.1.5+dfsg-1","7.2.0~beta1+dfsg-1","7.2.0~beta2+dfsg-1","7.2.0~rc1+dfsg-1","7.2.1+dfsg-1","7.2.2+dfsg-1","7.2.3+dfsg-1","7.2.4+dfsg-1","7.2.5+dfsg-1","7.2.6-1","7.3.0+dfsg-1","7.3.0~beta1+dfsg-1","7.3.0~beta2+dfsg-1","7.3.0~rc1+dfsg-1","7.3.1+dfsg-1","7.3.2+dfsg-1","7.3.3+dfsg-1","7.3.4+dfsg-1","7.3.5-1","7.4.0+dfsg-1","7.4.0+dfsg-2","7.4.0~beta1-1","7.4.0~beta1-2","7.4.0~beta2+dfsg-1","7.4.0~beta2+dfsg-2","7.4.0~beta2+dfsg-3","7.4.0~rc1+dfsg-1","7.4.0~rc2+dfsg-1","7.4.0~rc3+dfsg-1","7.4.10+dfsg-1","7.4.12+dfsg-1","7.4.13+dfsg-1","7.4.13+dfsg-2","7.4.14+dfsg-1","7.4.15+dfsg-1","7.4.15+dfsg-2","7.4.16+dfsg-1","7.4.17+dfsg-1","7.4.18+dfsg-1","7.4.19+dfsg-1","7.4.2+dfsg-1","7.4.2+dfsg-2","7.4.20+dfsg-1","7.4.21+dfsg-1","7.4.21+dfsg-2","7.4.22+dfsg-1","7.4.23+dfsg-1","7.4.3+dfsg-1","7.4.4+dfsg-1","7.4.5+dfsg-1","7.4.6+dfsg-1","7.4.6+dfsg-2","7.4.7+dfsg-1","7.4.8+dfsg-1","7.4.9+dfsg-1","8.0.0+dfsg-1","8.0.0~beta2+dfsg-1","8.0.0~beta2+dfsg-2","8.0.0~rc1+dfsg-1","8.0.0~rc2+dfsg-1","8.0.0~rc3+dfsg-1","8.0.10-1","8.0.11+dfsg-1","8.0.12+dfsg-1","8.0.13+dfsg-1","8.0.2+dfsg-1","8.0.3+dfsg-1","8.0.4+dfsg-1","8.0.5+dfsg-1","8.0.6+dfsg-1","8.0.7+dfsg-1","8.0.8+dfsg-1","8.0.9+dfsg-1","8.1.0+dfsg-1","8.1.1+dfsg-1","8.1.10+dfsg-1","8.1.11+dfsg-1","8.1.3+dfsg-1","8.1.4+dfsg-1","8.1.5+dfsg-1","8.1.6+dfsg-1","8.1.7+dfsg-1","8.1.8+dfsg-1","8.1.9+dfsg-1","8.2.0~beta1+dfsg-1"]},{"source":"osv","ecosystem":"Debian:13","package":"symfony","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.50+dfsg-0+deb13u1"}]}],"versions":["6.4.21+dfsg-2","6.4.21+dfsg-2+deb13u1","6.4.24+dfsg-1","6.4.25+dfsg-1","6.4.40+dfsg-0+deb13u1","6.4.41+dfsg-0+deb13u1","6.4.49+dfsg-0+deb13u1"]},{"source":"osv","ecosystem":"Debian:14","package":"symfony","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.4.23+dfsg-1"}]}],"versions":["6.4.21+dfsg-2","6.4.24+dfsg-1","6.4.25+dfsg-1","7.0.4+dfsg-1","7.0.5+dfsg-1","7.0.6+dfsg-1","7.0.7+dfsg-1","7.1.0~beta1+dfsg-1","7.1.0~rc1+dfsg-1","7.1.2+dfsg-1","7.1.3+dfsg-1","7.1.4+dfsg-1","7.1.5+dfsg-1","7.2.0~beta1+dfsg-1","7.2.0~beta2+dfsg-1","7.2.0~rc1+dfsg-1","7.2.1+dfsg-1","7.2.2+dfsg-1","7.2.3+dfsg-1","7.2.4+dfsg-1","7.2.5+dfsg-1","7.2.6-1","7.3.0+dfsg-1","7.3.0~beta1+dfsg-1","7.3.0~beta2+dfsg-1","7.3.0~rc1+dfsg-1","7.3.1+dfsg-1","7.3.2+dfsg-1","7.3.3+dfsg-1","7.3.4+dfsg-1","7.3.5-1","7.4.0+dfsg-1","7.4.0+dfsg-2","7.4.0~beta1-1","7.4.0~beta1-2","7.4.0~beta2+dfsg-1","7.4.0~beta2+dfsg-2","7.4.0~beta2+dfsg-3","7.4.0~rc1+dfsg-1","7.4.0~rc2+dfsg-1","7.4.0~rc3+dfsg-1","7.4.10+dfsg-1","7.4.12+dfsg-1","7.4.13+dfsg-1","7.4.13+dfsg-2","7.4.14+dfsg-1","7.4.15+dfsg-1","7.4.15+dfsg-2","7.4.16+dfsg-1","7.4.17+dfsg-1","7.4.18+dfsg-1","7.4.19+dfsg-1","7.4.2+dfsg-1","7.4.2+dfsg-2","7.4.20+dfsg-1","7.4.21+dfsg-1","7.4.21+dfsg-2","7.4.22+dfsg-1","7.4.3+dfsg-1","7.4.4+dfsg-1","7.4.5+dfsg-1","7.4.6+dfsg-1","7.4.6+dfsg-2","7.4.7+dfsg-1","7.4.8+dfsg-1","7.4.9+dfsg-1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"symfony","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.7.1+dfsg-1","2.7.5+dfsg-1","2.7.9+dfsg-1","2.7.9+dfsg-1ubuntu2","2.7.10-0ubuntu2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"symfony","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.8.7+dfsg-1.3ubuntu1","3.4.3+dfsg-1ubuntu4","3.4.6+dfsg-1","3.4.6+dfsg-1ubuntu0.1","3.4.6+dfsg-1ubuntu0.1+esm1","3.4.6+dfsg-1ubuntu0.1+esm2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"symfony","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.3.4+dfsg-1ubuntu1","4.3.8+dfsg-1ubuntu1","4.3.8+dfsg-1ubuntu1+esm1","4.3.8+dfsg-1ubuntu1+esm2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:22.04:LTS","package":"symfony","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.2.6+dfsg-1ubuntu7","5.4.4+dfsg-1ubuntu8","5.4.4+dfsg-1ubuntu8+esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:24.04:LTS","package":"symfony","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.23+dfsg-1ubuntu1","5.4.35+dfsg-3ubuntu1","6.4.5+dfsg-3ubuntu2","6.4.5+dfsg-3ubuntu3","6.4.5+dfsg-3ubuntu3+esm1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"symfony","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.4.7+dfsg-1ubuntu1","7.4.9+dfsg-1ubuntu1","7.4.13+dfsg-2ubuntu1","7.4.14+dfsg-1ubuntu2","7.4.15+dfsg-2ubuntu2","7.4.16+dfsg-1ubuntu2"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"symfony","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.4.24+dfsg-1","7.4.5+dfsg-1ubuntu1","7.4.6+dfsg-2ubuntu1","7.4.7+dfsg-1ubuntu1"]}],"products":[{"vendor":"sensiolabs","product":"symfony"},{"vendor":"symfony","product":"symfony"}],"references":[{"url":"https://github.com/symfony/symfony/security/advisories/GHSA-hqp2-7rr8-hf26","tags":["third-party-advisory","advisory","report"]},{"url":"https://github.com/symfony/symfony/commit/fcaf87a93c7fa5b7fe9e9e8382d4ed0d0c52c67c","tags":["patch","fix","report"]},{"url":"https://github.com/symfony/symfony/commit/9f7390678a255f7962fb1c81c42b26fa907d3437","tags":["patch","fix","report"]},{"url":"https://packagist.org/packages/symfony/serializer","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/122xxx/CVE-2026-122053.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-122053","tags":["advisory"]},{"url":"https://github.com/symfony/serializer","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-122053","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-122053","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-122053","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2026-122053","title":"Symfony: ObjectNormalizer Dotted-Key Property-Path Traversal Bypasses #[Ignore] on Nested Objects","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.\nObjectNormalizer::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-\u003ecustomer-\u003eadmin. 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.\n\nThe 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.","status":"published","published":"2026-11-06T16:46:46.986Z","modified":"2026-11-06T20:39:54.876Z","cvss":[{"version":"4.0","score":6.9,"vector":"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","level":"medium","assessor":"cna"},{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","level":"medium","assessor":"adp"}],"cwes":["CWE-915"],"updated_at":"2026-11-06T21:31:07.264033Z"}],"euvd":[{"id":"EUVD-2026-118360","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.\nObjectNormalizer::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-\u003ecustomer-\u003eadmin. 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.\n\nThe 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.","status":"published","published":"2026-11-06T16:46:46Z","modified":"2026-11-06T20:39:54Z","cvss":[{"version":"4.0","score":6.9,"vector":"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","level":"medium"}],"updated_at":"2026-11-06T22:07:15.91214Z"}],"nvd":[{"id":"CVE-2026-122053","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.\nObjectNormalizer::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-\u003ecustomer-\u003eadmin. 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.\n\nThe 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.","status":"published","published":"2026-11-06T17:17:20.123Z","modified":"2026-11-06T21:40:43.45Z","cvss":[{"version":"4.0","score":6.9,"vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium","assessor":"secondary"},{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-915"],"updated_at":"2026-11-07T00:02:36.552517Z"}],"osv":[{"id":"CVE-2026-122053","title":"Symfony: ObjectNormalizer Dotted-Key Property-Path Traversal Bypasses #[Ignore] on Nested Objects","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.\nObjectNormalizer::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-\u003ecustomer-\u003eadmin. 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.\n\nThe 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.","status":"published","published":"2026-11-06T16:46:46.986Z","modified":"2026-11-08T02:47:29.055988132Z","cvss":[{"version":"4.0","score":6.9,"vector":"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","level":"medium"}],"cwes":["CWE-915"],"updated_at":"2026-11-08T02:57:14.556074Z"},{"id":"DEBIAN-CVE-2026-122053","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-\u003ecustomer-\u003eadmin. 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.","status":"published","published":"2026-11-06T17:17:20.123Z","modified":"2026-11-10T00:00:07.177099061Z","cvss":[{"version":"4.0","score":6.9,"vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"medium"}],"updated_at":"2026-11-10T00:12:24.06296Z"},{"id":"UBUNTU-CVE-2026-122053","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-\u003ecustomer-\u003eadmin. 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.","status":"published","published":"2026-11-09T00:00:00Z","modified":"2026-11-10T02:50:13.586115418Z","cvss":[{"version":"4.0","score":6.9,"vector":"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","level":"medium"},{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-10T03:18:58.105788Z"}]}}