CVE-2025-65951: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in mescuwa entropy-derby
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.
AI Analysis
Technical Summary
CVE-2025-65951 concerns a cryptographic vulnerability in the mescuwa entropy-derby product, a research-grade horse-racing betting engine that uses a Verifiable Delay Function (VDF) based timelock encryption system to secure bet tickets. The vulnerability arises because, prior to commit 2d38d2f, the system failed to enforce the sequential delay property of the Wesolowski VDF against the betting operator. Bettors could pre-compute the entire VDF output (vdfOutputHex) and embed it within their encrypted bet tickets. This allowed the house to bypass the intended time delay by verifying the VDF proof quickly instead of performing the expensive sequential VDF evaluation. Consequently, the betting operator could decrypt bet tickets immediately, exposing sensitive betting information prematurely. This breaks the confidentiality and integrity guarantees of the betting process, potentially enabling unfair advantages or manipulation. The flaw is categorized under CWE-200 (Exposure of Sensitive Information) and CWE-327 (Use of a Broken or Risky Cryptographic Algorithm). The vulnerability affects all versions before commit 2d38d2f16bbb3b4240698148f80d8c5202725c77 and was publicly disclosed on November 25, 2025. The CVSS v3.1 score is 8.7 (High), reflecting network attack vector, low attack complexity, requirement of high privileges, no user interaction, and a scope change with high confidentiality and integrity impacts but no availability impact. No known exploits have been reported in the wild. The patch fixes the enforcement of the sequential delay, ensuring that the betting operator cannot shortcut the VDF evaluation process.
Potential Impact
For European organizations, especially those operating or regulating online betting platforms, this vulnerability poses significant risks. The premature exposure of sensitive bet information can undermine the fairness and trustworthiness of betting operations, potentially leading to financial losses, reputational damage, and regulatory penalties. Confidentiality breaches could allow malicious actors or insiders to gain unfair advantages or manipulate betting outcomes. Integrity of the betting process is compromised, which may affect customer confidence and market stability. Given the high CVSS score and the critical role of cryptographic timelocks in ensuring fair betting, failure to patch could lead to exploitation scenarios where attackers or insiders decrypt bets early, enabling fraud or insider trading. The impact is heightened in jurisdictions with strict gambling regulations and consumer protection laws, where such vulnerabilities could trigger legal consequences. Additionally, the vulnerability could be leveraged in complex fraud schemes or money laundering activities, further complicating compliance efforts.
Mitigation Recommendations
European organizations using entropy-derby should immediately upgrade to the patched version incorporating commit 2d38d2f16bbb3b4240698148f80d8c5202725c77 or later. Beyond patching, organizations should conduct a thorough cryptographic audit to verify correct implementation of VDFs and other cryptographic primitives, ensuring no similar bypasses exist. Implement runtime monitoring to detect anomalous betting patterns or unusually fast decryption attempts that could indicate exploitation. Restrict high-privilege access to cryptographic components and bet ticket processing systems to minimize insider threats. Employ defense-in-depth by segregating duties between bet submission and bet processing roles. Regularly review and update security policies related to cryptographic operations and betting integrity. Engage with vendors and the open-source community to stay informed about further vulnerabilities or patches. Finally, conduct penetration testing focused on cryptographic components to proactively identify weaknesses.
Affected Countries
United Kingdom, Germany, Malta, France, Netherlands, Italy, Spain
CVE-2025-65951: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in mescuwa entropy-derby
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.
AI-Powered Analysis
Technical Analysis
CVE-2025-65951 concerns a cryptographic vulnerability in the mescuwa entropy-derby product, a research-grade horse-racing betting engine that uses a Verifiable Delay Function (VDF) based timelock encryption system to secure bet tickets. The vulnerability arises because, prior to commit 2d38d2f, the system failed to enforce the sequential delay property of the Wesolowski VDF against the betting operator. Bettors could pre-compute the entire VDF output (vdfOutputHex) and embed it within their encrypted bet tickets. This allowed the house to bypass the intended time delay by verifying the VDF proof quickly instead of performing the expensive sequential VDF evaluation. Consequently, the betting operator could decrypt bet tickets immediately, exposing sensitive betting information prematurely. This breaks the confidentiality and integrity guarantees of the betting process, potentially enabling unfair advantages or manipulation. The flaw is categorized under CWE-200 (Exposure of Sensitive Information) and CWE-327 (Use of a Broken or Risky Cryptographic Algorithm). The vulnerability affects all versions before commit 2d38d2f16bbb3b4240698148f80d8c5202725c77 and was publicly disclosed on November 25, 2025. The CVSS v3.1 score is 8.7 (High), reflecting network attack vector, low attack complexity, requirement of high privileges, no user interaction, and a scope change with high confidentiality and integrity impacts but no availability impact. No known exploits have been reported in the wild. The patch fixes the enforcement of the sequential delay, ensuring that the betting operator cannot shortcut the VDF evaluation process.
Potential Impact
For European organizations, especially those operating or regulating online betting platforms, this vulnerability poses significant risks. The premature exposure of sensitive bet information can undermine the fairness and trustworthiness of betting operations, potentially leading to financial losses, reputational damage, and regulatory penalties. Confidentiality breaches could allow malicious actors or insiders to gain unfair advantages or manipulate betting outcomes. Integrity of the betting process is compromised, which may affect customer confidence and market stability. Given the high CVSS score and the critical role of cryptographic timelocks in ensuring fair betting, failure to patch could lead to exploitation scenarios where attackers or insiders decrypt bets early, enabling fraud or insider trading. The impact is heightened in jurisdictions with strict gambling regulations and consumer protection laws, where such vulnerabilities could trigger legal consequences. Additionally, the vulnerability could be leveraged in complex fraud schemes or money laundering activities, further complicating compliance efforts.
Mitigation Recommendations
European organizations using entropy-derby should immediately upgrade to the patched version incorporating commit 2d38d2f16bbb3b4240698148f80d8c5202725c77 or later. Beyond patching, organizations should conduct a thorough cryptographic audit to verify correct implementation of VDFs and other cryptographic primitives, ensuring no similar bypasses exist. Implement runtime monitoring to detect anomalous betting patterns or unusually fast decryption attempts that could indicate exploitation. Restrict high-privilege access to cryptographic components and bet ticket processing systems to minimize insider threats. Employ defense-in-depth by segregating duties between bet submission and bet processing roles. Regularly review and update security policies related to cryptographic operations and betting integrity. Engage with vendors and the open-source community to stay informed about further vulnerabilities or patches. Finally, conduct penetration testing focused on cryptographic components to proactively identify weaknesses.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-11-18T16:14:56.692Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6924fa182a08b12b0e784280
Added to database: 11/25/2025, 12:36:40 AM
Last enriched: 11/25/2025, 12:51:26 AM
Last updated: 11/25/2025, 3:03:28 AM
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-6389: CWE-94 Improper Control of Generation of Code ('Code Injection') in Sneeit Sneeit Framework
CriticalCVE-2025-59373: CWE-732 Incorrect Permission Assignment for Critical Resource in ASUS MyASUS
HighCVE-2023-41419: n/a
UnknownCVE-2025-9803: CWE-287 Improper Authentication in lunary-ai lunary-ai/lunary
CriticalCVE-2025-65944: CWE-201: Insertion of Sensitive Information Into Sent Data in getsentry sentry-javascript
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.