Vulnerability record

CVE-2024-36111

A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.

Full record read. Reported values and explicit gaps below come from the tracked record. Tracker snapshot: Aug 9, 2026.

What it is

Reported

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. Source description excerpt; complete tracked detail loads below.

NVD published: Jul 25, 2024 · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026

What is affected

Reported

1Panel — KubePi. Product-level identification only; no affected-version conclusion is available from this field.

NVD published: Jul 25, 2024 · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026

Urgency and basis

Reported

Act · 446.1

Tracker decision tier from the evidence detailed below · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026

Exploitation evidence

Reported

kev-listed · VulnCheck KEV

VulnCheck KEV added: Dec 3, 2024 · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026

What to do

Reported

Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Tracked source remediation field · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026

Evidence detail

Loading the full tracker evidence record…