/

CVE-2026-92720

Severity:

CRITICAL RISK

(9.1)

Missing Authentication (CWE-306) in Kubero Notifications

CVE-2026-92720

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthorized access, credential disclosure, webhook manipulation, and alerting disruption

Severity:

CRITICAL RISK

(9.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Kubero notification API endpoints do not consistently enforce authentication, allowing unauthenticated attackers to access webhook secrets and service URLs.

An attacker may also register malicious webhooks or delete existing configurations, which could expose pipeline events, redirect notifications, or suppress alerting when the endpoints are reachable.

Affected context

The vulnerability occurs in Kubero's notifications API when endpoint-level authentication guards are absent or bypassed. It becomes risky when the API is network-accessible and stores webhook credentials, service URLs, or notification configurations without requiring a valid authenticated session.

Exploit preconditions

  • Attack surface: Kubero notifications API endpoints
  • Required access: Network reachability to the affected API; valid credentials may not be required
  • Trigger point: Requests to read, create, or delete notification and webhook configurations
  • Why exploitation is possible: Missing authentication checks allow endpoint operations to proceed without verifying the caller's identity or privileges

Why this happens

The underlying bug is an authorization boundary failure in which sensitive API operations are exposed without a preceding authentication check. This maps to CWE-306: Missing Authentication for Critical Function, because the application permits access to protected functionality without establishing that the requester is an authenticated principal. The insecure pattern includes relying on routing or frontend access controls instead of enforcing authentication consistently at every sensitive API endpoint.

Potential impact

  • Webhook secrets and service URLs may be disclosed
  • Attackers could retrieve credentials for connected services
  • Malicious webhooks could be registered to intercept pipeline events
  • Existing notification configurations could be deleted
  • Alerting could be suppressed or redirected
  • Pipeline metadata or operational information could be exposed
  • Compromised webhook credentials could enable follow-on attacks against integrated systems

General mitigation guidance

Mitigation generally focuses on enforcing authentication and authorization at the API boundary for every sensitive notification operation.

Common defensive patterns include:

  • Applying authentication middleware consistently to read, create, update, and delete endpoints
  • Enforcing operation-level authorization and least-privilege permissions
  • Avoiding reliance on client-side, network-location, or frontend-only access controls
  • Limiting exposure of webhook secrets and service URLs in API responses
  • Using scoped credentials and rotating secrets when disclosure is suspected
  • Requiring explicit authorization for webhook registration and deletion
  • Applying secure-by-default network policies that restrict administrative APIs
  • Auditing access to notification resources and separating management from event delivery

How teams detect issues like this

Organizations can look for missing authentication through:

  • Static analysis rules identifying sensitive routes without authentication middleware
  • Code review checks that trace every notification operation to an identity and permission check
  • API inventory comparisons to confirm that administrative endpoints have consistent security policies
  • Integration tests that issue unauthenticated requests and verify denial by default
  • Runtime monitoring for anonymous reads, webhook creation, secret access, and configuration deletion
  • Policy enforcement requiring authentication and authorization annotations on protected API routes

Automated application-security testing and neutral code-review tools may help identify inconsistent endpoint guards.

Sources

SourceLink
github.comgithub.com/kubero-dev/kubero
github.comgithub.com/kubero-dev/kubero/blob/v3.1.1/server/src/main.ts
github.comgithub.com/kubero-dev/kubero/blob/v3.1.1/server/src/notifications/notifications.controller.ts#L23-L33
github.comgithub.com/kubero-dev/kubero/issues/753
vulncheck.comvulncheck.com/advisories/kubero-through-3.1.1-unauthenticated-notifications-api-access

Frequently asked

questions

It may be remotely exploitable when the Kubero notifications API is reachable by an attacker and the affected endpoints accept unauthenticated requests.

The key prerequisite is network access to the exposed API. The vulnerability is particularly serious because valid application credentials may not be required.

Require authentication and operation-specific authorization at every sensitive API endpoint, including read, create, update, and delete operations.

Maintain an API security inventory, enforce authentication by default, test anonymous access in CI, minimize secret exposure, and monitor administrative actions involving webhooks and notification configurations.

Find out what's already
exploitable in your codebase.