Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-61500 – Unauthenticated RCE via Predictable Session-Cookie Signing Key – Rejetto HFS 3.0…

Be the first to know when new zero-days emerge:

Summary

CVE-2026-61500 is a critical unauthenticated remote code execution vulnerability in Rejetto HFS (HTTP File Server) versions 3.0.0 through 3.2.0, scoring 9.3 (CRITICAL) under CVSS v4.0. The flaw stems from the application deriving its session-cookie signing key from JavaScript’s non-cryptographic Math.random() generator while simultaneously leaking outputs of that same generator to unauthenticated clients during the login flow. An attacker can exploit this entirely over the network, with no credentials required, to forge an administrator session cookie and achieve remote code execution. Rejetto has released version 3.2.1 to address the issue.

Technical details

  • Root cause: The session-cookie signing key is derived from Math.random(), a non-cryptographic pseudo-random number generator (PRNG), classified under CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator). Browser-grade PRNGs are predictable once a sufficient number of outputs are observed.
  • Trigger conditions: No authentication, no user interaction, and no special network position are required. The attack is entirely passive and opportunistic — the attacker only needs to send a small number of standard HTTP login requests to the exposed HFS instance.
  • Attack chain:
    1. Attacker sends a small number of login requests to the target HFS instance.
    2. HFS login responses disclose Math.random() outputs to the unauthenticated client.
    3. Attacker collects these outputs and uses them to reconstruct the internal PRNG state.
    4. With the PRNG state recovered, the attacker derives the session-cookie signing key.
    5. Attacker forges a valid administrator session cookie.
    6. Using the forged administrator cookie, the attacker accesses the server_code configuration feature to execute arbitrary code on the server.
  • Attack vector: Remote, over HTTP/HTTPS — no local access or network adjacency required.
  • Impact: Full administrative access and unauthenticated remote code execution (RCE) on the host running HFS.

Affected software

  • Rejetto HFS (HTTP File Server) 3.0.0 through 3.2.0 (all releases in this range are vulnerable)

Severity

  • CVSS v4.0: 9.3 (CRITICAL) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
  • CVSS v3.1: 9.8 (CRITICAL) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate action — patch: Upgrade to Rejetto HFS 3.2.1 or later. The vendor confirmed in the v3.2.1 release that this version resolves security vulnerabilities in all prior versions that could allow an attacker to gain administrative access to HFS.
  • If immediate patching is not feasible:
    • Restrict access to the HFS instance at the network perimeter — do not expose HFS directly to the internet.
    • Apply firewall or reverse-proxy rules to limit login endpoint access to trusted IP ranges only.
    • Monitor for anomalous or repeated unauthenticated login attempts in HFS access logs, which may indicate active PRNG state reconstruction attempts.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge