What’s Vulnerable › Vulnerabilities

CVE-2024-36111: KubePi's JWT token validation has a defect

• Severity: medium (CVSS 6.3 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 8.4% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2024-07-25 · updated 2026-06-17
• Weakness: CWE-1259

Description

KubePi is a K8s panel. Starting in version 1.6.3 and prior to version 1.8.0, there is a defect in the KubePi JWT token verification. The JWT key in the default configuration file is empty. Although a random 32-bit string will be generated to overwrite the key in the configuration file when the key is detected to be empty in the configuration file reading logic, the key is empty during actual verification. Using an empty key to generate a JWT token can bypass the login verification and directly take over the back end. Version 1.8.0 contains a patch for this issue.

Affected products

• 1Panel Dev Kubepi: from 1.6.3 before 1.8.0 — fixed in 1.8.0

How to fix

Upgrade to a fixed version: 1Panel Dev Kubepi 1.8.0. Check the vendor advisory for mitigations.

References

• https://github.com/1Panel-dev/KubePi/security/advisories/GHSA-8q5r-cvcw-4wx7
• https://github.com/1Panel-dev/KubePi/security/advisories/GHSA-8q5r-cvcw-4wx7

Get alerted when CVE-2024-36111 or the next vulnerability affects your stack