Quick answers
- Is CVE-2026-112380 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112380 being exploited in the wild.
- How severe is CVE-2026-112380?
- Critical severity, with a CVSS score of 9.9, published 20 October 2026.
- Which products and versions are affected?
- Kiro Crew 0.4.0 to 0.7.1.
- Is there a fix for CVE-2026-112380?
- Yes: fixed in 0.7.2. Until then: Remove all entries from whatsapp.groups configuration and keep whatsapp.dm_policy set to self (the default setting), which ensures group traffic is dropped before dispatch. Alternatively, disable the WhatsApp channel entirely until the upgrade is applied.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-20"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112380 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-112380?
- Check whether you run Amazon AWS or Kiro Crew 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: 0.7.2
Remove all entries from whatsapp.groups configuration and keep whatsapp.dm_policy set to self (the default setting), which ensures group traffic is dropped before dispatch. Alternatively, disable the WhatsApp channel entirely until the upgrade is applied.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-10-20"}]
Technical details
The vulnerability is an authorization bypass in Kiro Crew's WhatsApp channel and subagent run-control endpoints. An authenticated member of an operator-configured WhatsApp group can send instructions to other sessions' subagents, which execute those instructions under the receiving session's approval policy while attributing the audit trail to the operator. The attack requires the WhatsApp group to be explicitly listed in the configuration; the default configuration is not affected since whatsapp.groups defaults to empty and dm_policy defaults to self.
Affected products
- Kiro Kiro Crew 0.4.0 to 0.7.1