# CVE-2026-79403: Missing authorization in n/a

> A local attacker can execute arbitrary code via the permission/allow-everything endpoint in Kilo Code.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-vmfg-8hhv-69wh

## What is CVE-2026-79403?

CVE-2026-79403 is a high-severity missing authorization vulnerability in n/a, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in Kilo Code before v7.4.1 allows a local attacker to execute arbitrary code via the permission/allow-everything endpoint

Weakness: CWE-280 (Improper Handling of Insufficient Permissions or Privileges)

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


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

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

## Is CVE-2026-79403 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79403 is a high-severity missing authorization vulnerability in n/a, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-79403 in the wild and no public exploit code.

Affected product: n/a. 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-79403/ (Markdown: https://insights.sbomify.com/CVE-2026-79403/index.md)
```

## Sources

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

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