CVE-2026-125370: Kubero 3.0.0 through 3.1.1 Authentication Bypass via Hardcoded JWT Secret

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of 13 Nov 2026. If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?

0.7%

EPSS score, percentile 53.1 of all scored records. A probability estimated by FIRST, not a report of exploitation.

CISA's SSVC assessment in the CVE record lists exploitation as poc.

How severe?

9.3 Critical

CVSS v4.0 base score, given by the CNA

What should I do?

CISA has set no required action, because the vulnerability is not in KEV.

No patch or vendor advisory is listed in the CVE record. Check kubero-dev's advisories.

Which versions are affected?

Affected

• 3.0.0 through 3.1.1

Versions by product

Source: CISA KEV 2026.11.13, as of 13 Nov 2026; FIRST EPSS, as of 13 Nov 2026; CVE List, as of 14 Nov 2026. About the data.

Description

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.

Source: CVE List, as of 14 Nov 2026. About the data.

What to do

Advisories and patches

No patch, vendor advisory or mitigation is listed in the CVE record. Check kubero-dev's own security advisories for a fix, and compare your version with the affected versions below.

This summary is based on the CVE record as of 14 Nov 2026. Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

Source: CVE List, as of 14 Nov 2026. About the data.

Timeline