Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/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
PR:L because crafting/injecting content blocks needs authoring access; integrity I:H (Object.prototype corruption) dominates, with C:L/A:L for cross-tenant leakage and possible DoS; S:U per vendor though cross-tenant argues S:C.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
3DescriptionCVE.org
Builder.io Gen2 SDKs through versions 5.2.11 and 0.25.13 contain a prototype pollution vulnerability in the deep-set helper function that processes content block bindings without validation. Attackers can craft content blocks with binding keys containing __proto__, prototype, or constructor paths to pollute Object.prototype during rendering, affecting all subsequent objects created in the process including other tenants' renders.
AnalysisAI
Prototype pollution in Builder.io Gen2 SDKs at versions ≤5.2.11 (React, Vue, Svelte, Solid) and ≤0.25.13 (Qwik, Angular, React Next.js) lets an attacker who can supply a malicious content block - for example an authenticated content editor or author with write access to a Builder.io space - inject binding keys containing __proto__, prototype, or constructor paths that the deep-set helper processes during block rendering without validation. The result is pollution of Object.prototype with high integrity impact (VI:H) and limited confidentiality/availability impact (C:L/A:L): every object created later in the same process inherits the tainted properties, so in multi-tenant or shared SSR/rendering deployments one tenant's crafted content can contaminate other tenants' renders. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires the ability to supply a malicious content block with attacker-controlled binding keys (e.g. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | This is a genuine but conditional risk, not a top-tier emergency. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | No vendor-released patch version was identified in the available intelligence at time of analysis, so confirm current status at the upstream issue https://github.com/BuilderIO/builder/issues/4823 and the repository https://github.com/BuilderIO/builder before planning an upgrade; once a fixed release is published, upgrade every affected package past the vulnerable ceilings (5.2.11 for the React/Vue/Svelte/Solid SDKs and 0.25.13 for the Qwik/Angular/React-Next.js SDKs). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all deployments using Builder.io Gen2 SDKs at versions ≤5.2.11 for React, Vue, Svelte, and Solid and ≤0.25.13 for Qwik, Angular, and React Next.js, identify multi-tenant or shared SSR environments, restrict content editor or author write access to trusted personnel, and audit recent content blocks for binding keys containing __proto__, prototype, or constructor. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Prototype Pollution
View allPrototype pollution in Adobe Acrobat Reader versions 24.001.30356, 26.001.21367 and earlier enables arbitrary code execu
Prototype pollution in the farinspace Partners WordPress plugin (versions up to and including 0.2.0) enables remote unau
Prototype pollution vulnerability in 'deephas' versions 1.0.0 through 1.0.5 allows attacker to cause a denial of service
A Prototype Pollution issue in Cronvel Tree-kit v.0.7.4 and before allows a remote attacker to execute arbitrary code vi
A Prototype Pollution issue in Aliconnect /sdk v.0.0.6 allows an attacker to execute arbitrary code via the aim function
All versions of the package safe-eval are vulnerable to Prototype Pollution via the safeEval function, due to improper s
This affects the package vm2 before 3.9.4 via a Prototype Pollution attack vector, which can lead to execution of arbitr
Prototype Pollution in chargeover redoc v2.0.9-rc.69 allows attackers to execute arbitrary code or cause a Denial of Ser
alizeait unflatto <= 1.0.2 was discovered to contain a prototype pollution via the method exports.unflatto at /dist/inde
A vulnerability exists in the 'dagre-d3-es' Node.js package version 7.0.9, specifically within the 'bk' module's addConf
A Prototype Pollution vulnerability in the util-deps.addFileDepend function of magix-combine-ex versions thru 1.2.10 all
Chartist 1.x through 1.3.0 allows Prototype Pollution via the extend function. Rated critical severity (CVSS 9.8), this
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-81042
GHSA-4qmr-g3pc-xvhm