Skip to main content
VulnerabilityPublished

CVE-2026-125370: kubero · Use of Hard-coded Cryptographic Key

Affects kuberoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical.

Data as of 10 Nov 2026, 00:02 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.09.3
CNA (VulnCheck)CVSS 3.19.8
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
kubero-devkuberoAffected
  • >=3.0.0 <=3.1.1
Fixed in–

AI-suggested

As a mitigation, ensure that the JWT_SECRET environment variable is properly set to a secure value to prevent fallback to the hardcoded signing secret.

Description

Kubero versions 3.0.0 through 3.1.1 contain an authentication bypass vulnerability due to a hardcoded fallback JWT signing secret. When the JWT_SECRET environment variable is unset, attackers can forge administrative JWT tokens with arbitrary claims, gaining control over pipelines, applications, users, and API tokens.

References

Community reviews

Loading reviews…