# CVE-2026-92720: Kubero through 3.1.1 Unauthenticated Notifications API Access

> Unauthenticated attackers can access Kubero notifications API to steal webhook secrets and modify alerting configurations.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-m69f-42c6-7334

## What is CVE-2026-92720?

CVE-2026-92720 is a critical missing authorization vulnerability in kubero-dev kubero, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Kubero through 3.1.1 fails to apply authentication guards to the notifications API endpoints, allowing unauthenticated attackers to read webhook secrets and service URLs. Attackers can retrieve stored credentials and register malicious webhooks to intercept pipeline events or suppress alerting by deleting existing configurations.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-92720?


## How do I fix CVE-2026-92720?

No fix has been published for CVE-2026-92720 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92720 being exploited?

There is no known exploitation of CVE-2026-92720 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92720 and fix it if it is affected.

What it is: CVE-2026-92720 is a critical missing authorization vulnerability in kubero-dev kubero, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92720 in the wild and no public exploit code.

Affected product: kubero-dev kubero. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92720/ (Markdown: https://insights.sbomify.com/CVE-2026-92720/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92720
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92720
- OSV: https://osv.dev/vulnerability/CVE-2026-92720

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92720/
Summaries are generated and may contain mistakes; the official description above is the record.