CVE-2026-92717

Covenant through version 0.6 registers its CovenantHub SignalR hub without an Authorize attribute, so any unauthenticated caller who can reach the Covenant web interface can invoke CreateHttpListener and receive a signed JWT token. With that token, the attacker authenticates as an operator against the full Covenant API and can access grunts (implants), captured credentials, binaries, tasking events, and the operator roster. Any team running Covenant 0.6 or earlier is affected, especially where the Covenant web/API port is reachable beyond localhost. No public proof-of-concept, KEV listing, or confirmed in-the-wild exploitation is currently known, although the flaw requires no authentication or user interaction and is trivially reachable where the interface is exposed.

What to do: Restrict access to the Covenant web/API and SignalR ports to trusted management networks or a VPN, and apply an upstream fix adding the Authorize attribute to CovenantHub as soon as a patched release is available. Organizations that ran Covenant on internet-reachable hosts should assume operator API compromise: rotate the JWT signing key and any credentials stored in the Covenant database, and audit API logs for unauthenticated hub connections or unknown operator activity.