affected products in the CVE record: sensiolabs · symfonythe product type of Symfony in nday's product registry
stage
DIS
disclosed
cvss
6.9 MEDIUM v4.0
# Lifecycle
x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet
# Summary
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.
Original text of the CVE record (cvelist), shown as published.
# Exploit conditions
What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no target-specific security measures to get around
Attack requirements AT:N
None: success does not depend on how the target is deployed or running
Your account is suspended: you cannot comment, reply, edit or report. You can still delete your own comments.
formatting
↵↵
empty line: new paragraph
↵
line break: kept as is
*…*
emphasis
**…**
bold
`…`
inline code
```
on its own line: starts and ends a code block
> …
quote
- …
list
1. …
numbered list
[…](https://…)
link (http and https only)
https://…
bare address: link
CVE-2026-1234
links to that vulnerability on nday
\*
shows the character itself
Headings, images, tables, nested lists and HTML are shown as plain text.
Links from new accounts are shown as plain text; CVE IDs are always linked.
reported
# Keyboard shortcuts
j / k
next / previous row (list rows or events)
Enter
open the vulnerability under the cursor
/
search (Esc leaves the box)
y
copy the CVE ID
o
open the event's source (vulnerability page)
u
back
?
show / hide this help
sign inaccountmodadminAdminProfileFollowingSecurityDeveloperSign outSigned in.Sign-in method linked to your account.Sign-in was cancelled at the provider; nothing changed.That login already belongs to another nday account, or this account already has one from the same provider. Nothing was linked.Sign-in did not complete. Try again.You are still signed in as before: that login belongs to another nday account, or to none yet. Sign out first to use it.Linking was not completed because your last sign-in is no longer recent. Confirm it's you on the account page, then link again.This account is suspended, so new sign-in methods cannot be linked.Dismissworking…Delete this comment? This cannot be undone.Hidden by a moderator: {reason}text (moderators only)earlier versions: {n}replaced at {time}Posting needs the community rules accepted (version {version}).The community rules changed (version {version}); read and accept them to continue.Reported. A moderator will look at it.You have already reported this comment.You are signed out. Sign in again to continue.The request was refused as cross-site. Reload the page and try again.The session token changed. Reload the page and try again.Your account is suspended.Choose a handle on your account page first.Accept the current community rules first.Only moderators can do this.Only the author can do this.You cannot report your own comment.This comment changed in the meantime. Reload the page to see it as it is now.This comment or vulnerability does not exist (any more).Not a valid CVE ID.Only a visible top-level comment can get replies.This thread has reached its reply limit.You posted the same text here a moment ago.A comment needs 1 to {max} characters.Comments cannot be posted from this site language.Unknown purpose, or a purpose on a reply. Reload the page and try again.The reason is missing or too long.The note is too long.Unknown resolution.This position in the list is no longer valid. Reload the page.The request was malformed. Reload the page and try again.The text is too large.Too many requests. Try again in {seconds} s.Too many requests. Try again later.Daily limit reached. Try again after {time}.The server is busy. Try again in a moment.This address does not take comments. Open the page on the main site.Server error. Try again later.Network error: nday could not be reached. Check the connection and try again.The community rules changed while you were reading. Read them again.Write something first.Too long: {n} characters, at most {max}.Tick the box to accept the community rules first.Something went wrong ({code}). Try again.No comments yet.The discussion could not be loaded right now.more commentsfirst commentsmore repliesreplies[deleted account]link to this commenteditedposted on the {language} siteHidden by a moderator.Deleted by its author.technical analysisreproduction reportfix reportdetection methodquestionPlease include the affected version, the environment (OS, configuration), what you did and what happened, and your source.Please include the fixed version or patch, the environment, how you checked the fix and what happened, and your source.show {n} moreview on XThe posts could not be loaded.nday has not collected any post on X by listed researchers that mentions this CVE.expandcollapsesending…Sent. An editor will look at it; you can follow its status here.titlesummaryaffected products or versionsfix informationtimeline eventsource linksotherwaiting for an editoracceptednot acceptedsent {at}Editors' note: {note}Sign in first.Your account is suspended.Choose a public handle on your account page first.Accept the current community rules on your account page first.The page's session expired; try again.The request was refused; reload the page and try again.Choose what is wrong.Write what is wrong, within the length limit.The evidence link must be a full http:// or https:// address.You already have several reports on this vulnerability waiting for an editor; wait until they are handled.This vulnerability already has many reports waiting for an editor; try again later.You reached the limit of reports for 24 hours; try again later.Too many requests; wait a moment and try again.This vulnerability was not found.The report is too large.Network error; try again.Write what is wrong first.Too long: at most {max} characters.Something went wrong; try again later.