Process-wide object corruption via unsafe binding paths
Published Sep 16, 2026 · Updated Sep 17, 2026
Prototype pollution in Builder.io Gen2 SDKs through 5.2.11 and 0.25.13 allows remote authenticated users to corrupt process-wide objects. The binding evaluator passes attacker-controlled content keys into a deep-set helper that accepts proto, prototype, and constructor path segments and writes through them to Object.prototype. The attacker must control a rendered content block; polluted properties affect later objects in the process and can cross tenant render boundaries.
Summary
What happened
Prototype pollution in Builder.io Gen2 SDKs through 5.2.11 and 0.25.13 allows remote authenticated users to corrupt process-wide objects. The binding evaluator passes attacker-controlled content keys into a deep-set helper that accepts proto, prototype, and constructor path segments and writes through them to Object.prototype. The attacker must control a rendered content block; polluted properties affect later objects in the process and can cross tenant render boundaries.
The record
- CVE
- CVE-2026-92779
- Published
- Sep 16, 2026
- Updated
- Sep 17, 2026
- Vendor
- Builder.io
- Product
- @builder.io/sdk-solid
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=5.2.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Builder Gen 2 SDK prototype-pollution proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started