CVE-2026-61500

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-13. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 the same generator to unauthenticated clients during login. A remote attacker can collect a small number of login responses, reconstruct the generator's state, recover the signing key, and forge a valid administrator session cookie, leading to full administrative access and remote code execution via the server_code configuration feature.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
—
EPSS
51.0%
KEV
Not listed

Published

July 13, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated Jul 16, 2026
Patch available. Sources: github_release.
generic

Rejetto HFS < 3.2.1 Session Forgery via Predictable Signing Key | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rejetto-hfs-session-forgery-via-predictable-signing-key
github_release Patch Available

3.2.1

Patch available: rejetto/hfs v3.2.1

https://github.com/rejetto/hfs/releases/tag/v3.2.1

Vendor Advisories for CVE-2026-61500(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-17 03:05 UTCGHSA enrichment
  10. 2026-07-16 23:14 UTCGHSA enrichment
  11. 2026-07-16 19:22 UTCGHSA enrichment
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-16 15:29 UTCGHSA enrichment
  14. 2026-07-16 11:36 UTCGHSA enrichment
  15. 2026-07-16 07:45 UTCGHSA enrichment
  16. 2026-07-16 03:53 UTCGHSA enrichment
  17. 2026-07-16 00:02 UTCGHSA enrichment
  18. 2026-07-15 20:11 UTCGHSA enrichment
  19. 2026-07-15 16:57 UTCEPSS rescore
  20. 2026-07-15 16:20 UTCGHSA enrichment
  21. 2026-07-15 12:29 UTCGHSA enrichment
  22. 2026-07-15 08:37 UTCGHSA enrichment
  23. 2026-07-15 04:44 UTCGHSA enrichment
  24. 2026-07-15 02:00 UTCEPSS rescore
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 10 more
  1. 2026-07-15 00:48 UTCGHSA enrichment
  2. 2026-07-14 20:56 UTCGHSA enrichment
  3. 2026-07-14 17:05 UTCGHSA enrichment
  4. 2026-07-14 13:14 UTCGHSA enrichment
  5. 2026-07-14 09:21 UTCGHSA enrichment
  6. 2026-07-14 05:27 UTCGHSA enrichment
  7. 2026-07-14 01:36 UTCGHSA enrichment
  8. 2026-07-13 21:45 UTCGHSA enrichment
  9. 2026-07-13 17:53 UTCEG score recompute
  10. 2026-07-13 17:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-61500?
CVE-2026-61500 is a critical vulnerability published on July 13, 2026. 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 the same generator to unauthenticated clients during login. A remote attacker can collect a small number of login responses, reconstruct the generator's…
When was CVE-2026-61500 disclosed?
CVE-2026-61500 was first published in the National Vulnerability Database on July 13, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61500 actively exploited?
CVE-2026-61500 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 51.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-61500?
CVE-2026-61500 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-61500?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61500, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-61500

Explore →

Is Your Infrastructure Affected by CVE-2026-61500?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs