Quick answers
- Is CVE-2026-92781 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92781 being exploited in the wild.
- How severe is CVE-2026-92781?
- Medium severity, with a CVSS score of 6.3, 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-92781?
- 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-92781 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-92781?
- 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
The vulnerability is a prototype pollution flaw in the unflatten helper function, which processes builder.userAttributes query parameters without proper prototype guards. Attackers can craft URLs containing __proto__ or prototype segments that, when processed by the SDK running in a visitor's browser, pollute Object.prototype and alter the behavior of JavaScript objects across the application. The attack vector is network-based and requires no authentication; victims need only visit a malicious link. An attacker can modify global object behavior, potentially causing denial of service, application logic hijacking, or information disclosure depending on how the affected application uses prototypes.
Affected products
- Builder.io Gen2 SDKs through 5.2.11 and 0.25.13
Timeline
- 2026-09-16: disclosed