Quick answers
- Is CVE-2026-92779 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92779 being exploited in the wild.
- How severe is CVE-2026-92779?
- High severity, with a CVSS score of 7.6, published 16 September 2026.
- Which products and versions are affected?
- Builder.Io Gen2 SDKs through 5.2.11 and 0.25.13.
- Is there a fix for CVE-2026-92779?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-92779 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-92779?
- Check whether you run Builder.Io Gen2 SDKs at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A prototype pollution vulnerability exists in the deep-set helper function used to process content block bindings within the Gen2 SDKs. The vulnerable code fails to validate binding keys before assignment, allowing attackers to craft content blocks containing malicious keys such as __proto__, prototype, or constructor that pollute Object.prototype during rendering. The attack requires network access to provide crafted content blocks to the SDK rendering engine. Successful exploitation enables arbitrary property injection into the global object prototype, potentially leading to code execution or denial of service affecting all subsequent object creation. Multi-tenant environments are particularly at risk, as prototype pollution can cross tenant boundaries during concurrent render operations.
Affected products
- Builder.io Gen2 SDKs through 5.2.11 and 0.25.13
Timeline
- 2026-09-16: disclosed