CVE-2025-61928VulnerabilityPublished 20 Oct 2025

CVE-2025-61928: Better-Auth Critical Account Takeover via Unauthenticated API Key Creation

Source Reddit NetSec

Not known to be exploited · 18% EPSS.

Data as of 25 Oct 2026, 19:02 UTC

Severity

Critical

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 18.8% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
Public on cve.org; its publication date is not in this record
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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

European organizations should immediately audit their use of Better-Auth, particularly focusing on applications with API key functionality enabled. Until an official patch is released, disable API key creation features or restrict them to authenticated and authorized users only. Implement strict monitoring and alerting for unusual API key creation activities and review logs for signs of unauthorized access. Employ network segmentation and least privilege principles to limit the impact of any compromised accounts. Update dependency management practices to quickly incorporate security patches once available. Engage with the Better-Auth community and maintain awareness of official advisories and patches. Consider additional compensating controls such as multi-factor authentication (MFA) for API key usage and rotating existing API keys to invalidate potentially compromised keys. Conduct penetration testing focused on authentication and API key management to identify residual risks. Finally, prepare incident response plans specific to account takeover scenarios to reduce response times in case of exploitation.

Description

CVE-2025-61928 is a critical vulnerability in the Better-Auth authentication library, widely used in applications with API key functionality enabled. This flaw allows unauthenticated attackers to create API keys, leading to complete account takeover without requiring user interaction or prior authentication. With approximately 300,000 weekly downloads, this vulnerability potentially affects a large number of projects and organizations relying on Better-Auth for authentication. Although no known exploits are currently observed in the wild, the ease of exploitation and the critical impact on confidentiality, integrity, and availability make this a high-risk threat. European organizations using Better-Auth in their applications are at significant risk of unauthorized access and data compromise. Immediate mitigation involves disabling API key creation until patches are available, implementing strict API key management policies, and monitoring for suspicious API key generation activities. Countries with high software development activity and extensive use of open-source JavaScript libraries, such as Germany, the UK, France, and the Netherlands, are most likely to be impacted. Given the critical nature of the vulnerability and the broad scope of affected systems, organizations must prioritize remediation efforts to prevent account takeovers and potential downstream attacks.

Impact

For European organizations, the impact of CVE-2025-61928 is substantial. Organizations relying on Better-Auth for API key management face the risk of unauthorized account access, leading to data breaches, unauthorized transactions, and potential lateral movement within networks. This can result in loss of sensitive customer data, intellectual property, and disruption of services. The critical nature of the vulnerability means attackers can fully compromise user accounts without detection, undermining trust and regulatory compliance, especially under GDPR. The potential for widespread exploitation could affect sectors such as finance, healthcare, e-commerce, and government services that depend on secure authentication mechanisms. Additionally, compromised accounts could be leveraged for further attacks, including privilege escalation and ransomware deployment. The lack of known exploits currently provides a window for proactive mitigation, but the high download volume and open-source nature of Better-Auth increase the likelihood of rapid exploitation once detailed technical information becomes widely available.

Summary

The vulnerability identified as CVE-2025-61928 affects Better-Auth, a popular authentication library with around 300,000 weekly downloads, commonly used in web applications to manage API keys and user authentication. The flaw allows attackers to create API keys without any authentication, effectively bypassing all access controls. This unauthenticated API key creation leads to a complete account takeover, granting attackers full access to user accounts and potentially sensitive data. The vulnerability arises from improper validation and authorization checks in the API key creation process within Better-Auth. Since API keys often provide broad access privileges, their unauthorized creation can compromise confidentiality, integrity, and availability of affected applications. The vulnerability does not require user interaction and can be exploited remotely, increasing the attack surface. Although no public patches or exploits are currently documented, the critical severity and widespread use of Better-Auth necessitate urgent attention. The lack of a CVSS score requires an assessment based on the impact and exploitability, which is deemed critical due to the total compromise potential and ease of exploitation. The vulnerability was disclosed via a Reddit NetSec post, indicating early-stage public awareness but limited discussion or mitigation guidance so far.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 20 Oct 2025, 19:49 UTC

Technical details

References

Community reviews

Related threats