# CVE-2026-107785: Crux Agent silently fails SKA preshared key rotation when SHA-512 peering is negotiated

> Crux Agent fails to rotate WireGuard preshared keys correctly when SHA-512 is negotiated, potentially allowing decryption of traffic by quantum-capable attackers.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:U/S:N/AU:Y/R:A/V:C/RE:L/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-jm3h-x845-c42w

## What is CVE-2026-107785?

CVE-2026-107785 is a medium-severity vulnerability in Sirius Computer, Inc. Crux Agent, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Crux Agent from 1.9.0 before 2.0.3 uses the full SKA bilocation key as the WireGuard preshared key. When a peering session negotiates use of SHA-512, the key produced is 64 bytes instead of the 32 bytes WireGuard requires. The agent does not validate this size; instead it attempts to use the `wg set` command to update the live tunnel, and write the invalid key to the WireGuard configuration file. The update fails, so the live tunnel keeps using its previous preshared key until the tunnel is shut down. The tunnel will fail to start when restarted.

For a peer which has never successfully negotiated a 32-byte bilocation key in a Crux C2 organization which has the "Enforce SKA Use" setting turned off, no preshared key will be set for the tunnel. Therefore, an attacker who is able to intercept and store the peer's traffic, and has access (or will have access) to a cryptographically relevant quantum computer, will be able to decrypt the tunnel.

Weakness: CWE-394 (Unexpected Status Code or Return Value), CWE-325 (Missing Cryptographic Step), CWE-252 (Unchecked Return Value)

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


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

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

## Is CVE-2026-107785 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107785 is a medium-severity vulnerability in Sirius Computer, Inc. Crux Agent, published on 9 Oct 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-107785 in the wild and no public exploit code.

Affected product: Sirius Computer, Inc. Crux Agent. 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-107785/ (Markdown: https://insights.sbomify.com/CVE-2026-107785/index.md)
```

## Sources

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

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