CVE-2026-125370

waiting for further signalsZero needs more public information before it can validate it.

GHSA-42fc-m93g-j65w ↗EUVD-2026-120533 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
kubero-dev kubero >= 3.0.0, <= 3.1.1
CWE-321 Use of Hard-coded Cryptographic Key
ETK-2026-4011Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 06h 23msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h55m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Kubero versions 3.0.0 through 3.1.1 are affected when JWT_SECRET is unset. A remote unauthenticated attacker may obtain administrative access by creating tokens that the application accepts with attacker-chosen privileges.

mitigation

Set JWT_SECRET to a unique, high-entropy secret and restart Kubero so it does not use its fallback signing key. Restrict public access to the service until a vendor-fixed release is available.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-09 23:27Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-09 23:27Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-125370

{
  "etk_id": "ETK-2026-4011",
  "cve_id": "CVE-2026-125370",
  "display_id": "CVE-2026-125370",
  "ghsa_id": "GHSA-42fc-m93g-j65w",
  "euvd_id": "EUVD-2026-120533",
  "status": "published",
  "anchor_state": "anchored",
  "title": "JWT authentication bypass in Kubero",
  "summary": "Kubero versions 3.0.0 through 3.1.1 are affected when JWT_SECRET is unset. A remote unauthenticated attacker may obtain administrative access by creating tokens that the application accepts with attacker-chosen privileges.",
  "mitigation": "Set JWT_SECRET to a unique, high-entropy secret and restart Kubero so it does not use its fallback signing key. Restrict public access to the service until a vendor-fixed release is available.",
  "vendor": "kubero-dev",
  "product": "kubero",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.0.0, <= 3.1.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "kubero",
      "purl": null
    }
  ],
  "cwes": [
    321
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.1450998,
  "t0_at": "2026-11-09T23:27:41.949000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-09T23:27:41.949000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-09T23:27:41.949000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-125370"
    }
  }
}

published 2026-11-10 00:11Z
last change 2026-11-11 05:12Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.