home / blog
2026-11-10 · critical
CVE-2026-125370: Authentication Bypass in Kubero 3.0-3.1.1
Authentication bypass in Kubero 3.0-3.1.1: unauthenticated attackers forge admin tokens and control the system.

CVE-2026-125370 identifies a critical authentication vulnerability in Kubero versions 3.0.0 through 3.1.1. The flaw consists of a hardcoded JWT signing secret used as a fallback when the JWT_SECRET environment variable is not configured. Unauthenticated attackers can exploit this misconfiguration to forge arbitrary JWT tokens with administrative permissions, completely bypassing the authentication mechanism.
The vulnerability carries a CVSS score of 9.8 (critical). The validation mechanism (JwtStrategy.validate()) accepts forged tokens without performing database verification, granting complete control over pipelines, applications, user management, and API tokens. As of publication date (2026-11-10), no official patch is available. Signals from social networks confirm community attention to the criticality of this flaw.
System administrators running Kubero must act immediately. First, verify whether Kubero is deployed in production environments. If present, isolate or disable external access to services until a patch is available. Configuring JWT_SECRET with a strong value across all environments is essential. Continuously monitor official Kubero team communications for a fix announcement and plan the upgrade as soon as it becomes available.
At a glance
- What
- Authentication bypass vulnerability in Kubero versions 3.0.0 to 3.1.1. A hardcoded JWT signing secret is used as a fallback when JWT_SECRET environment variable is not set. Unauthenticated attackers can forge arbitrary administrative JWT tokens that JwtStrategy.validate() accepts without database verification, allowing control over pipelines, applications, users, and API tokens.
- Severity
- CVSS 9.8 (Critical). The vulnerability enables full administrative control of the system without authentication.
- Affected versions
- Kubero versions 3.0.0 through 3.1.1.
- Fix
- Not confirmed - no patch has been released according to available signals as of 2026-11-10.
- Status
- Vulnerability published on 2026-11-10. Activity present on social networks but no confirmed public exploit repositories.
- Action
- Verify whether Kubero is in use in production environments. Isolate its exposed services if possible. Monitor Kubero team communications for security patches. Do not wait passively.
Sources: NVD, CVE-2026-125370