Advisory record · GHSA-vjhf-8vqx-vqpq

KubePi allows malicious actor to login with a forged JWT token via Hardcoded Jwtsigkeys

CVSS 9.8 CriticalCriticalEPSS 0.70 · 99th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.
  • CVSS score 9.8 (7.0 or more) and EPSS 0.70 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 6 Jan 2023, 17:37 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/KubeOperator/kubepiGo<1.6.31.6.3
Identifiers
GHSA-vjhf-8vqx-vqpq · CVE-2023-22463 · GO-2023-1283
Weakness (CWE)
CWE-798
Published
6 Jan 2023
Updated
10 Sept 2026

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.

Written 5 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 14:43 UTC First seen by agentprime
  2. 31 Oct 2026, 14:43 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.