CVE-2026-92779
Builder.io Gen2 SDKs through 5.2.11 Prototype Pollution via Bindings
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- BuilderIO @builder.io/sdk-react
through 5.2.11
- BuilderIO @builder.io/sdk-vue
through 5.2.11
- BuilderIO @builder.io/sdk-svelte
through 5.2.11
- BuilderIO @builder.io/sdk-solid
through 5.2.11
- BuilderIO @builder.io/sdk-qwik
through 0.25.13
- BuilderIO @builder.io/sdk-angular
through 0.25.13
- BuilderIO @builder.io/sdk-react-nextjs
through 0.25.13