Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.9

CVE-2026-125370: Kubero lets attackers bypass login using default token key

CVE-2026-125370 · published 12 days ago
Summary

Kubero versions 3.0.0 to 3.1.1 will use a built-in secret key if the custom key is not set. This lets an outside attacker create their own admin tokens and gain full control of the system. Upgrade to a newer version or configure a unique secret key immediately to stop the risk.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
VendorProductAffected versions
kubero-dev kubero <= 3.1.1
Original advisory text
Kubero 3.0.0 through 3.1.1 Authentication Bypass via Hardcoded JWT Secret
Kubero 3.0.0 through 3.1.1 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to forge administrative JWTs by using a hardcoded fallback signing secret when JWT_SECRET is unset. Attackers can sign tokens with arbitrary role, userGroups and permissions claims, which JwtStrategy.validate() trusts without a database lookup, to take control of pipelines, applications, users and API tokens.
Fix within
Internet-facing 3 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically
  • Gives an attacker full control
Severity
9.9 Critical
Exploitation
<1% chance of attack within 30 days
Type
CWE-321Use of Hard-coded Cryptographic Key
Timeline
Published9 Nov 2026
Updated22 Nov 2026
First seen10 Nov 2026
Sources
CVE-2026-125370 · MITRE
Track software like this
Free during beta