CVE-2025-65951: mescuwa entropy-derby · Information Exposure
Affects mescuwa entropy-derbySource CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Operators should immediately update entropy-derby to versions including or later than commit 2d38d2f16bbb3b4240698148f80d8c5202725c77, which patches the vulnerability by enforcing proper sequential delay in the VDF timelock encryption. Additionally, organizations should audit their betting ticket generation and verification processes to ensure no pre-computed VDF outputs are accepted. Implement strict access controls to limit high-privilege operations to trusted personnel only. Monitoring and logging of betting ticket submissions and decryptions should be enhanced to detect anomalous patterns indicative of pre-computation attempts. Regular cryptographic code reviews and penetration testing focused on VDF implementations are recommended to prevent similar issues. Finally, organizations should engage with regulatory bodies to report remediation status and ensure compliance with data protection and gambling fairness standards.
Description
Inside Track / Entropy Derby is a research-grade horse-racing betting engine. Prior to commit 2d38d2f, the VDF-based timelock encryption system fails to enforce sequential delay against the betting operator. Bettors pre-compute the entire Wesolowski VDF and include vdfOutputHex in their encrypted bet ticket, allowing the house to decrypt immediately using fast proof verification instead of expensive VDF evaluation. This issue has been patched via commit 2d38d2f.