CVE-2024-36111

High PUBLISHED

KubePi's JWT token validation has a defect

1Panel-dev · KubePi

Not yet in CISA KEV

Exploited in the wild

Recommended Action

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Confidence
High
Exploitation Status
Exploited in the wild
Observed in Sensors
No
Attempts (30d)
Unique Attacker IPs
CISA KEV
Not yet in CISA KEV
CVSS / EPSS
6.3 Medium

At a Glance

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.

CVE Published
Jul 25, 2024
Exploitation Reported
Jul 07, 2025
CVSS
6.3 Medium
EPSS
Remote Low complexity No user interaction

Affected Versions

Vendor Product Version Status
1panel_dev
kubepi

1.6.3 to < 1.8.0

Affected
1Panel-dev
KubePi

>= 1.6.3, < 1.8.0

Affected

CVE References

Recommended Actions

  • Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
  • Use the Pro API to automate enrichment, telemetry, and workflow delivery for VM, SOC, and CTI pipelines.