CVE Catalog

CVE-2026-107785

MediumCVSS 6.3
Published: Updated: Translated: NVD NIST

Summary

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 SHA-512, the key is 64 bytes instead of the required 32 bytes. The agent does not validate the size, causing failures in tunnel updates and configuration writes. For peers without a previously negotiated 32-byte key, the tunnel may have no preshared key, allowing an attacker with a quantum computer to decrypt traffic.

Risk Assessment

Lack of a proper preshared key may allow an attacker to intercept and decrypt tunneled traffic, posing a serious threat to data confidentiality.

Recommendation

It is recommended to update Crux Agent to version 2.0.3 or later, which includes a fix, and enable the "Enforce SKA Use" setting in the Crux C2 organization.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS