Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
KubePi versions before 1.6.3 (affected <1.6.3) use a hardcoded JWT signing key, so the same key is used across all installations. An attacker can forge JWT tokens and take over the administrator account without logging in. Upgrade to KubePi 1.6.3, which fixes the issue.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.8 | Critical | 3.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.70, the 99th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:43 UTC First seen by agentprime
- 31 Oct 2026, 14:43 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-vjhf-8vqx-vqpq
- OSV: GHSA-vjhf-8vqx-vqpq
- github.com/KubeOperator/KubePi/security/advisories/GHSA-vjhf-8vqx-vqpq
- nvd.nist.gov/vuln/detail/CVE-2023-22463
- github.com/KubeOperator/KubePi/commit/3be58b8df5bc05d2343c30371dd5fcf6a9fbbf8b
- github.com/KubeOperator/KubePi
- github.com/KubeOperator/KubePi/blob/da784f5532ea2495b92708cacb32703bff3a45a3/internal/api/v1/session/session.go#L35
- github.com/KubeOperator/KubePi/releases/tag/v1.6.3