# CVE-2026-92802: kan through 0.6.0 Authorization Bypass via GitHub Project Import

> Attackers can bypass authorization checks to create boards as guests, allowing unauthorized data modification in kan project management software.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-frgf-wpx9-58c9

## What is CVE-2026-92802?

CVE-2026-92802 is a medium-severity missing authorization vulnerability in kanbn kan, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

kan through 0.6.0 fails to properly validate board creation permissions in the GitHub project import endpoint, allowing guests to create boards despite lacking board:create permission. Attackers can bypass authorization checks by using the importProjects mutation to create boards while remaining blocked on direct creation paths.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-92802 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92802 is a medium-severity missing authorization vulnerability in kanbn kan, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92802 in the wild and no public exploit code.

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

## Sources

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

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