CVE-2026-92802 json
kan through 0.6.0 Authorization Bypass via GitHub Project Import
published 2026-09-16 53 d ago modified 2026-09-22 47 d ago also EUVD-2026-81062
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 52 d ago
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
| CNA | 4.0 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- kanbn kan
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
-
github.com
/kanbn/kan/issues/628
issue-tracking
-
github.com
/kanbn/kan
product
-
github.com
/kanbn/kan/blob/v0.6.0/packages/api/src/routers/import.ts#L622-L670
technical-description
-
github.com
/kanbn/kan/blob/f08920d/packages/api/src/routers/import.ts#L259
technical-description
-
vulncheck.com
/advisories/kan-through-0.6.0-authorization-bypass-via-github-project-import
third-party-advisory
Sources
- CVE List CVE-2026-92802
- NVD CVE-2026-92802
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.