# CVE-2026-112380: Missing authorization in the WhatsApp channel in Kiro Crew


- **Severity:** Critical 9.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-x4jf-p42g-q3hc

## What is CVE-2026-112380?

CVE-2026-112380 is a critical vulnerability in Amazon Kiro Crew, published on 20 Oct 2026. 

### Official description

Missing authorization in the WhatsApp group channel in Kiro Crew might allow a remote actor who is a member of an operator-configured WhatsApp group to control the operator's other agent sessions and execute arbitrary commands on the host running Kiro Crew via messages sent to the group.

To remediate this issue, users should upgrade to version 0.7.2.

Weakness: CWE-863 (Incorrect Authorization), CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-112380?


## How do I fix CVE-2026-112380?

No fix has been published for CVE-2026-112380 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112380 being exploited?

There is no known exploitation of CVE-2026-112380 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112380 and fix it if it is affected.

What it is: CVE-2026-112380 is a critical vulnerability in Amazon Kiro Crew, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112380 in the wild and no public exploit code.

Affected product: Amazon Kiro Crew. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112380/ (Markdown: https://insights.sbomify.com/CVE-2026-112380/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112380
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112380
- OSV: https://osv.dev/vulnerability/CVE-2026-112380

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112380/
Summaries are generated and may contain mistakes; the official description above is the record.