Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-92720 – Unauthenticated Credential Disclosure & Webhook Tampering – Kubero ≤ 3.1.1

Be the first to know when new zero-days emerge:

Summary

CVE-2026-92720 is a missing authentication vulnerability (CWE-306) in Kubero, an open-source, self-hosted Platform-as-a-Service for Kubernetes. The notifications API in Kubero versions through 3.1.1 lacks any authentication or authorization guard, allowing unauthenticated network attackers to read stored webhook secrets and service URLs, and to create, modify, or delete notification configurations. The issue carries a critical severity rating (9.3) due to its trivial exploitability, lack of any prerequisite access, and direct exposure of credentials that can be leveraged for further compromise.

Technical details

  • Root cause: The notifications controller in Kubero (notifications.controller.ts) does not apply the JwtAuthGuard/permission decorators used by sibling controllers (e.g., pipelines, config), leaving all of its routes open to unauthenticated access.
  • Affected endpoints: GET /api/notifications, GET /api/notifications/:id, POST /api/notifications, PUT /api/notifications/:id, and DELETE /api/notifications/:id.
  • Trigger conditions: No authentication, session, or prior access is required — a direct HTTP request to any of the affected endpoints on an exposed Kubero instance is sufficient.
  • Attack vector: Network-based, requiring no user interaction and no privileges (AV:N/PR:N/UI:N).
  • Impact: Exposed data includes webhook HMAC secrets, and Slack, Discord, and generic webhook URLs stored in cleartext. Attackers can use disclosed secrets to impersonate legitimate integrations, register attacker-controlled webhooks to exfiltrate pipeline/deployment events, tamper with existing notification targets to redirect alerts, or delete configurations to suppress security and operational alerting.

Affected software

  • Kubero (kubero-dev/kubero): all versions up to and including 3.1.1

Severity

  • CVSS v3.1: 9.1 (Critical) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
  • CVSS v4.0: 9.3 (Critical) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: As of this writing, no patched Kubero release addressing this issue has been published (3.1.1 remains the latest available version). Track the vendor’s GitHub repository and upgrade immediately once a fixed release is issued.
  • Workarounds / network mitigations:
    • Do not expose the Kubero API or web UI directly to the internet; restrict access to trusted internal networks or VPN.
    • Place an authenticating reverse proxy or API gateway in front of the Kubero instance to enforce access control on /api/notifications routes until an official fix is released.
    • Rotate all webhook secrets, Slack/Discord webhook URLs, and any credentials configured in Kubero notifications, since they may already be exposed.
    • Monitor logs for unauthenticated requests to /api/notifications* endpoints and for unexpected creation/modification/deletion of notification configurations.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge