CVE-2026-107785
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:Y/R:A/V:C/RE:L/U:Amber
Exploit Intelligence
Low risk: more likely to be exploited than 3% of all known CVEs.
References
Related Vulnerabilities
Other CWE-252 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2005-4360 | High | 7.8 | 87% | - | - |
| CVE-2026-111497 | Critical | 9.8 | 83% | KEV | Fix |
| CVE-2007-3798 | Critical | 9.8 | 70% | - | Fix |
| CVE-2010-0211 | Critical | 9.8 | 28% | - | Fix |
| CVE-2022-23626 | High | 8.5 | 9.9% | - | Fix |
| CVE-2019-10902 | High | 7.5 | 4.7% | - | - |
Common questions
How do I fix CVE-2026-107785?
No published fix for CVE-2026-107785 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-107785 being actively exploited?
Not that we know of. CVE-2026-107785 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.14% is the estimated probability that it will be exploited in the next 30 days. That is higher than 3% of all scored CVEs.
How severe is CVE-2026-107785?
CVE-2026-107785 has a CVSS v4 base score of 6.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-107785
Markdown
[](https://tridentstack.com/cve/CVE-2026-107785)HTML
<a href="https://tridentstack.com/cve/CVE-2026-107785"><img src="https://tridentstack.com/cve/badge/CVE-2026-107785.svg" alt="CVE-2026-107785"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-09.