PatchSiren cyber security CVE debrief
CVE-2025-71402 better-auth CVE debrief
An attacker can supply a forged _multi-* cookie to trigger deletion of arbitrary session tokens in better-auth versions greater than 1.3.34 and before 1.4.0 due to a vulnerability in the multi-session plugin's /sign-out after-hook. This occurs because the plugin trusts raw multi-session cookies and forwards extracted values to internalAdapter.deleteSessions without verifying the cookie signature.
- Vendor
- better-auth
- Product
- Unknown
- CVSS
- LOW 2
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-01
- Original CVE updated
- 2026-10-06
- Advisory published
- 2026-08-01
- Advisory updated
- 2026-10-06
Who should care
Defenders responsible for maintaining and securing applications that use the better-auth library, particularly those using versions greater than 1.3.34 and before 1.4.0, should be aware of this vulnerability. They should assess their exposure and take necessary actions to prevent potential session token deletion.
Why it matters
Defenders should care about CVE-2025-71402 because it allows an attacker to delete arbitrary session tokens in better-auth versions greater than 1.3.34 and before 1.4.0. This could disrupt user sessions and requires verification of affected versions and application of patches.
- Potential deletion of arbitrary session tokens
- Possible disruption to user sessions
- Need for verification of affected versions and application of patches
Technical summary
The better-auth library, used for authentication, has a vulnerability in its multi-session plugin. Specifically, the /sign-out after-hook does not properly verify the signature of multi-session cookies. This allows an attacker to forge a _multi-* cookie, which can then be used to trigger the deletion of arbitrary session tokens. The affected versions are greater than 1.3.34 and before 1.4.0. This vulnerability can lead to potential deletion of arbitrary session tokens and disruption of user sessions. Defenders should verify the affected version of better-auth and apply necessary patches to prevent potential session token deletion.
Defensive priority
Defenders should prioritize verifying the affected version of better-auth and applying the necessary patches to prevent potential session token deletion.
Recommended defensive actions
- Verify the version of better-auth in use and apply patches if necessary
- Review and update session management configurations to prevent potential session token deletion
- Monitor for potential exploitation attempts
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD entry provide details about the vulnerability in better-auth versions greater than 1.3.34 and before 1.4.0. The vulnerability allows an attacker to supply a forged _multi-* cookie to trigger deletion of arbitrary session tokens.
Sources and references
Verified primary and authoritative sources
-
CVE-2025-71402 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2025-71402
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2025-71402 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2025-71402
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/better-auth/better-auth/security/advisories/GHSA-wmjr-v86c-m9jj
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/better-auth-before-session-revocation-via-forged-cookie
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.