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

Back
New CVE Detected

CVE-2026-92717 – Unauthenticated Access to Operator API via SignalR Hub – Covenant ≤ 0.6

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-92717 is a missing-authentication vulnerability (CWE-306) in Covenant, an open-source .NET command-and-control (C2) framework, affecting all versions through 0.6. The CovenantHub SignalR hub is registered without an [Authorize] attribute, allowing unauthenticated attackers to invoke a method that returns a valid, long-lived JWT token. That token grants full access to the operator REST API, exposing active implant sessions, harvested credentials, exfiltrated files, and operator account details. The flaw carries a CVSS score of 9.3 (Critical).

Technical details

  • Root cause: The CovenantHub SignalR hub (Covenant/Hubs/CovenantHub.cs) is missing the [Authorize] attribute that is present on Covenant’s other SignalR hubs, leaving it reachable without authentication.
  • Trigger conditions: An unauthenticated client connects to the /covenanthub SignalR endpoint and invokes the CreateHttpListener method.
  • Attack vector: Network — no credentials, prior access, or user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: The invoked method returns a signed JWT (carrying a "Listener" role) with an approximately 2000-day expiration. Because Covenant’s REST API controllers only enforce a generic JWT-bearer policy without role checks, this token authorizes full access to the operator API — including grunt (implant) sessions, stored credentials, generated binaries/launchers, event logs, tasking data, and the operator account roster.

Affected software

  • Covenant (cobbr/Covenant) — all versions through 0.6, inclusive

Severity

  • CVSS v3.1 Base Score: 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 Score: 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: No patched release has been published at the time of this advisory. Monitor the upstream Covenant repository and Issue #406 for a fix and upgrade as soon as one is released.
  • If no patch is available: Restrict network access to the Covenant server (management interfaces, including the /covenanthub SignalR endpoint and REST API) to trusted operator networks only, e.g., via VPN, firewall allow-listing, or placing the deployment behind an authenticating reverse proxy. Do not expose Covenant C2 infrastructure directly to the internet. Rotate any credentials, session tokens, and grunt/implant secrets if exposure is suspected, and review access logs for unauthenticated SignalR connections or unexpected CreateHttpListener invocations.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge