CVE-2025-71403 better-auth CVE debrief

Who should care

Defenders responsible for better-auth deployments should assess exposure and prioritize verification of versions before 1.1.20. Security teams and vulnerability management teams should review the CVE details and assess the impact on their environments. Operators and administrators of affected systems should verify versions and implement additional security measures for sensitive token protection.

Why it matters

CVE-2025-71403 better-auth Open Redirect via trustedOrigins Bypass allows attackers to steal sensitive tokens. Defenders should verify better-auth versions and assess exposure to potential open redirect attacks.

• Potential for account takeover through sensitive token theft
• Open redirect attacks may lead to phishing or further exploitation
• Verification of better-auth versions and trustedOrigins configuration is necessary
• Additional security measures for sensitive token protection are recommended

Technical summary

better-auth versions before 1.1.20 contain a bypass vulnerability in trustedOrigins validation logic, allowing attackers to construct malicious callbackURL parameters that pass origin checks and trigger open redirects to steal sensitive tokens for account takeover. The vulnerability affects absolute URLs and wildcard domains. Defenders should prioritize verification of better-auth versions before 1.1.20 and assess exposure to potential open redirect attacks. This issue requires immediate attention to prevent potential account takeovers.

Defensive priority

Defenders should prioritize verification of better-auth versions before 1.1.20 and assess exposure to potential open redirect attacks.

Recommended defensive actions

• Verify better-auth version is 1.1.20 or later
• Assess exposure to potential open redirect attacks
• Implement additional security measures for sensitive token protection
• 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 on the better-auth open redirect vulnerability. Vendor advisories and vulnerability details are available through source references. The vulnerability has been publicly disclosed and defenders should verify better-auth versions and assess exposure to potential open redirect attacks. Evidence is limited to public sources and CVE details.

Sources and references

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.