Critical
CVE-2026-125370: Kubero Auth Bypass via Hardcoded JWT Secret
Inttelio Threat Feeds ·
Kubero versions 3.0.0 through 3.1.1 fall back to a hardcoded JWT signing secret when the JWT_SECRET setting is not configured. An unauthenticated remote attacker can use that secret to forge administrative tokens and take control of pipelines, applications, users and API tokens. The flaw is rated CVSS 3.1 9.8 (Critical).
| CVE | CVE-2026-125370 |
|---|---|
| CVSS v3.1 | 9.8 CRITICAL |
| Weakness | CWE-321 |
| Exploited in the wild | Not listed in CISA KEV |
| Published | November 10, 2026 |
Who is affected
Organizations running Kubero 3.0.0 through 3.1.1 where the JWT_SECRET environment variable is unset. In that state the application signs and accepts tokens using a hardcoded fallback secret (CWE-321, use of a hard-coded cryptographic key). A fixed version is not stated in the source data. Check the Kubero GitHub repository, issue #786, and the VulnCheck advisory for patch status.
What attackers can do
An attacker with network access to the Kubero instance needs no credentials and no user interaction. They can sign a JWT with the known fallback secret and set any role, userGroups and permissions claims they want. Kubero's JwtStrategy.validate() trusts these claims without checking the database, so the forged token is accepted as an administrator. With that access an attacker can take control of pipelines, applications, users and API tokens. Because Kubero deploys applications, this could let an attacker change or deploy workloads in your environment. The CVSS rating reflects high impact to confidentiality, integrity and availability.
Exploitation status
The source data contains no CISA Known Exploited Vulnerabilities (KEV) entry for this CVE, so there is no confirmed in-the-wild exploitation on record. The weakness is easy to abuse once the fallback secret is known, and the vulnerable code is publicly referenced. Treat it as high priority.
What to do now
- Inventory all Kubero deployments and identify any running versions 3.0.0 through 3.1.1.
- On every instance, set JWT_SECRET to a strong, randomly generated value that is unique to that instance, then restart Kubero. This removes reliance on the hardcoded fallback secret.
- Check the Kubero GitHub repository, issue #786, and the VulnCheck advisory for a fixed release. Upgrade once one is available. A fixed version is not stated in the source data.
- Restrict network access to the Kubero UI and API to trusted networks or a VPN until it is patched and configured.
- Look for signs of compromise. Review Kubero users, API tokens, pipelines and applications for unexpected additions or changes, and check access logs for unfamiliar sources.
- If you suspect compromise, take these steps: remove unauthorized users and tokens, rotate API tokens and any secrets managed by or exposed to Kubero, and review deployed workloads and the underlying Kubernetes cluster for unauthorized changes.
Frequently asked questions
Which Kubero versions are affected by CVE-2026-125370?
Kubero 3.0.0 through 3.1.1 are affected when the JWT_SECRET setting is unset. A fixed version is not stated in the source data. Check the Kubero GitHub project and the VulnCheck advisory.
Am I protected if I already set JWT_SECRET?
According to the description, the hardcoded fallback secret is used only when JWT_SECRET is unset. Instances with a strong, unique JWT_SECRET should not be exposed to this specific token forgery. Confirm the value is actually loaded at runtime, and upgrade once a fix is available.
Is CVE-2026-125370 being exploited in the wild?
The source data has no CISA KEV entry for this CVE, so no confirmed in-the-wild exploitation is on record. It is critical (CVSS 9.8), unauthenticated and low-complexity, so remediate it promptly.
Sources
- https://nvd.nist.gov/vuln/detail/CVE-2026-125370
- https://github.com/kubero-dev/kubero
- https://github.com/kubero-dev/kubero/blob/bcb52376b19347b8c36bc445ddf3e4bff4a5c168/server/src/auth/strategies/jwt.strategy.ts#L13-L32
- https://github.com/kubero-dev/kubero/issues/786
- https://www.vulncheck.com/advisories/kubero-3.0.0-through-3.1.1-authentication-bypass-via-hardcoded-jwt-secret
This briefing was drafted with AI from the official NVD and CISA records. Always confirm affected versions and fixes in the vendor advisory.
Not sure if you are exposed?
Our penetration testers find exploitable flaws before attackers do, and a vCISO can run your vulnerability program.
Talk to Inttelio