On this page (7 sections)

Kubero, a self-hosted platform for managing pipelines and applications, has a critical authentication bypass tracked as CVE-2026-125370. According to the GitHub Advisory, versions 3.0.0 through 3.1.1 fall back to a hardcoded signing secret when the JWT_SECRET setting is not provided, which lets an unauthenticated remote attacker create administrator tokens.

If you run Kubero, especially on a network-reachable address, check whether JWT_SECRET is set in your deployment today. This article explains the weakness, how to check exposure, and what to do while patch details are unclear.

What happened

The flaw was published on November 10, 2026 in the National Vulnerability Database and the GitHub Advisory Database. The description says unauthenticated remote attackers can forge administrative JSON Web Tokens (JWTs) by using a hardcoded fallback signing secret that the application uses when JWT_SECRET is unset. The advisory links to a VulnCheck advisory and a Kubero issue (#786).

Only one independent publisher covers this so far. The NVD entry repeats the same description, so it is not separate confirmation. The GitHub advisory is marked unreviewed and lists affected and patched versions as unknown, so treat the version range in the CVE description as the best available guidance.

How the weakness works

A JWT is a signed token the server hands out after login. On each request the server checks the signature and, if it is valid, trusts what the token says about the user. The security of the whole scheme depends on the signing secret being private and unpredictable.

Here, when JWT_SECRET is not configured, Kubero signs and verifies tokens with a secret that is written into the source code. Anyone who can read the public code can know that value. Per the advisory, an attacker can then sign tokens containing any role, userGroups and permissions claims. The JwtStrategy.validate() function trusts those claims without a database lookup, so a forged token is treated as a real administrator. The relevant source file is public in the project repository.

The advisory states the impact as control over pipelines, applications, users and API tokens. The CVSS v4 metrics list network attack vector, low complexity, no privileges and no user interaction required, with high confidentiality, integrity and availability impact on the vulnerable system.

Who is exposed

The condition that matters is a Kubero instance in the 3.0.0 to 3.1.1 range where JWT_SECRET was never set. Instances that already have a strong, unique JWT_SECRET configured should not depend on the fallback value, though the sources do not say this explicitly, so verify rather than assume.

Realistic exposure is highest for instances reachable from the internet or from broad internal networks, such as test installs, quick-start deployments and anything deployed from default settings. Because Kubero manages applications and API tokens, a takeover can reach well beyond Kubero itself, into whatever those applications and tokens can touch.

How to check your exposure

First confirm which Kubero version you run, using your deployment tooling or the version shown in your installation. Then check whether JWT_SECRET is defined in the environment of the Kubero server. If Kubero runs on Kubernetes, this read-only command describes the deployment, including its environment variables. Replace the placeholders with your own deployment name and namespace, run it where kubectl is configured, and look for JWT_SECRET in the output:

Describe a Kubernetes deployment and its environment variables (read-only, run where kubectl is…Shell
kubectl describe deployment <kubero-deployment-name> -n <namespace>

If JWT_SECRET is injected from a Kubernetes secret, the output shows a reference to that secret rather than the value, which is what you want. If you deploy with Docker or another method, inspect the same environment settings in your compose file, manifest or secret store. If JWT_SECRET is missing or empty, treat the instance as vulnerable while it runs a version in the affected range.

What to do now

  1. Identify every Kubero instance you run and note its version (3.0.0 through 3.1.1 is affected).
  2. Check whether JWT_SECRET is set for each instance; if not, treat it as exposed.
  3. Set JWT_SECRET to a long, random, unique value generated for that instance, store it as a secret, and restart Kubero so it takes effect.
  4. Restrict network access to Kubero with a VPN, IP allowlist or authenticating reverse proxy until you are confident it is safe.
  5. Watch the Kubero repository and issue 786 for a fixed release, and upgrade once one is confirmed.
  6. If the instance was reachable while JWT_SECRET was unset, review users, API tokens, pipelines and applications for changes you did not make, and rotate API tokens and any credentials Kubero holds.
  7. Expect users to sign in again after the change: a new signing secret invalidates tokens signed with the old one.
Caution. Restarting Kubero after setting JWT_SECRET will interrupt the management interface briefly and sign users out. Plan it for a quiet window and keep a copy of the new secret in your secret manager.
The sources do not name a patched version. Do not assume a specific upgrade fixes the issue until the maintainers or the advisory confirm it. Setting your own JWT_SECRET addresses the described condition, but this article cannot confirm that it is a complete fix.

Detection and monitoring

A forged token looks like a valid administrator session, so ordinary login logs may show nothing unusual. Look instead for administrative actions with no matching login: new or changed users, newly created API tokens, modified pipelines, and applications deployed or altered at unexpected times. Review access logs of any reverse proxy in front of Kubero for requests to administrative API paths from unfamiliar addresses.

After remediation, keep Kubero off the open internet where you can, and make sure its address is covered by your normal monitoring. You can use Webforta Monitor for uptime, certificate and DNS change alerts on the hostname that serves it, and the free SSL checker to confirm the certificate is valid. These do not detect this flaw, but they help you notice unexpected changes around the service. For broader guidance on handling a suspected takeover, see website hacked: what to do.

The wider lesson is that management planes should not be reachable by untrusted networks and should never rely on default secrets.

Timeline

Known dates from the sources
DateEvent
Nov 10, 2026CVE-2026-125370 published by NVD and added to the GitHub Advisory Database
Nov 10, 2026GitHub advisory last updated; patched versions listed as unknown

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-125370 - GitHub Advisory Databasegithub.com
  2. CVE-2026-125370: Kubero 3.0.0 through 3.1.1 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to forge administrative JWTs by using…nvd.nist.gov ·
  • Kubero
  • JWT
  • authentication bypass
  • Kubernetes
  • CVE-2026-125370