• Sources: primary, fix release, research index, exploitation report, discussion
  • Summary: GHSA-xxrm-3f86-v97j records that Rejetto HFS 3.0.0 through 3.2.0 derives its session-cookie signing key from the non-cryptographic Math.random() generator and discloses outputs of that generator to unauthenticated clients during login, so an attacker can collect a small number of login responses, reconstruct the generator state, recover the key, and forge a valid administrator session cookie, which the advisory states leads to full administrative access and remote code execution through the server_code configuration feature. The advisory scores it CVSS v4 9.3 under CWE-338, carries the 3.0.0 through 3.2.0 range in its description text while its structured affected and patched fields read Unknown, references the v3.2.1 release tag as the fix, and was published 2026-07-13, well behind the current 3.3.4 of 2026-09-30. The Register quotes VulnCheck's Patrick Garrity describing exploitation beginning on the night of 2026-10-01 from a single China-hosted address against hosts in the United States and Japan, followed on 2026-10-02 by four attempts from two United States addresses in one subnet that appear to be a proxy. Garrity's tracker attributes 286 CVE records to Mythos and Project Glasswing, and he states this is the second of those known to be exploited. The Horizon3 attack research index carries a disclosure entry dated 2026-09-30 stating its researchers used Anthropic's Mythos to find the chain of cryptographic weaknesses, recover the signing key, forge an admin session, and reach remote code execution, and the firm's own write-up was not reachable from this environment.
  • Why it matters: HFS 3.0.0 through 3.2.0 are affected and 3.2.1 fixes it, so instances on the current 3.3.x line are already clear and the exposure is limited to unmaintained deployments, where the outcome is remote code execution rather than data exposure alone.
  • Follow-up: Watch for the Horizon3 write-up, and for the timeline discrepancy between The Register's 2026-09-30 discovery framing and the advisory's 2026-07-13 publication date.