# CVE-2026-92717: Covenant through 0.6 Missing Authentication on the CovenantHub SignalR Hub

> Unauthenticated attackers can invoke a SignalR hub to obtain a JWT token, granting full access to the operator API and sensitive C2 data.

- **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-h9hg-x52x-c465

## What is CVE-2026-92717?

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

### Official description

Covenant through 0.6 registers the CovenantHub SignalR hub without an Authorize attribute, allowing unauthenticated callers to invoke CreateHttpListener and receive a signed JWT token. Attackers can use the obtained token to authenticate against the entire operator API and access grunts, credentials, binaries, events, and the operator roster.

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

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


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

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

## Is CVE-2026-92717 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92717 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92717 is a critical missing authorization vulnerability in cobbr Covenant, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92717 exists.

Affected product: cobbr Covenant. 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-92717/ (Markdown: https://insights.sbomify.com/CVE-2026-92717/index.md)
```

## Sources

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

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