CVE-2026-15538
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA weakness has been identified in primefaces primereact up to 10.9.8. This issue affects the function ObjectUtils.mutateFieldData of the component API. This manipulation of the argument Field causes improperly controlled modification of object prototype attributes. The attack is possible to be carried out remotely. The project was informed of the problem early through an issue report but has not responded yet. This vulnerability only affects products that are no longer supported by the maintainer.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a Prototype Pollution vulnerability in PrimeReact's ObjectUtils.mutateFieldData function (versions up to 10.9.8). The function improperly allows modification of object prototype attributes, potentially enabling attackers to inject or manipulate object properties at the prototype level.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify PrimeReact versionRun 'npm list primereact' in your project directory or check package.json for the primereact dependency versionAffected if Version is 10.9.8 or earlier (any version up to and including 10.9.8)
-
Locate mutateFieldData usageSearch your codebase for calls to ObjectUtils.mutateFieldData or mutateFieldData (e.g., grep -r 'mutateFieldData' or IDE search)Affected if The function is called anywhere in your codebase
-
Verify input source to mutateFieldDataReview the code paths where data is passed to mutateFieldData and trace whether any user-controlled input (request parameters, form data, API payloads) reaches this functionAffected if User-controlled data flows into mutateFieldData without prior sanitization
-
Inspect sanitize logicLook for input validation or sanitization that strips or blocks __proto__, constructor, and prototype properties before passing data to mutateFieldDataAffected if No such sanitization exists for these prototype-affecting keys
You are affected if PrimeReact version 10.9.8 or earlier is installed AND your application uses mutateFieldData with data that could be influenced by external users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince this affects unsupported product versions, upgrade to a supported PrimeReact release if available; otherwise, implement input validation and defensive coding in mutateFieldData to prevent prototype pollution (e.g., block __proto__, constructor, and prototype in user-controlled input).
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15538 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15538 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data