Quick answers
- Is CVE-2026-78287 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78287 being exploited in the wild.
- How severe is CVE-2026-78287?
- Critical severity, with a CVSS score of 10, published 11 November 2026.
- Which products and versions are affected?
- STAGGS through 3.3.0.
- Is there a fix for CVE-2026-78287?
- Yes: fixed in 3.4.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-78287 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-78287?
- Check whether you run STAGGS 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.
How to fix
- Fixed in: 3.4.0
Technical details
An improper control of code generation vulnerability (CWE-94) in STAGGS allows unauthenticated remote code injection and execution. The vulnerability exists in code that dynamically generates or includes user-supplied input without proper sanitization, allowing attackers to break out of the intended context and execute arbitrary server-side commands. No authentication or user interaction is required to exploit this flaw.
Affected products
- STAGGS STAGGS through 3.3.0
Timeline
- 2026-11-09: disclosed: Reported by codelake Research on 2026-10-24; published 2026-11-09
- 2026-11-09: patched: Fixed in version 3.4.0