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 theJwtAuthGuard/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, andDELETE /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/notificationsroutes 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.

