better-auth
better-auth
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at better-auth, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2025-71401 | 2 Aug 2026 | better-auth: < 1.4.2 | better-auth: 1.4.2 | Update reference ↗ |
| CVE-2025-71399 | 2 Aug 2026 | better-auth: < 1.4.5 | better-auth: 1.4.5 | Update reference ↗ |
| CVE-2026-67336 | 1 Aug 2026 | < 1.6.11 | 1.6.11 | Update reference ↗ |
| CVE-2026-67333 | 1 Aug 2026 | < 1.6.13; 1.7.0-beta.0 < 1.7.0-beta.4 | 1.6.13; 1.7.0-beta.4 | Update reference ↗ |
| CVE-2026-67334 | 1 Aug 2026 | 0.3.4 < 1.6.11; 1.6.0 < 1.6.11 | 1.6.11 | Update reference ↗ |
| CVE-2025-71403 | 1 Aug 2026 | better-auth: < 1.1.20 | better-auth: 1.1.20 | Update reference ↗ |
| CVE-2026-67337 | 1 Aug 2026 | < 1.4.9 | 1.4.9 | Update reference ↗ |
| CVE-2025-71404 | 1 Aug 2026 | better-auth: < 1.1.16 | better-auth: 1.1.16 | Update reference ↗ |
| CVE-2026-67327 | 1 Aug 2026 | 1.1.3 < 1.6.22; 1.7.0-beta.0 < 1.7.0-beta.10 | 1.6.22; 1.7.0-beta.10 | Update reference ↗ |
| CVE-2026-67335 | 1 Aug 2026 | < 1.6.2 | 1.6.2 | Update reference ↗ |
| CVE-2025-71402 | 1 Aug 2026 | better-auth: < 1.4.0 | better-auth: 1.4.0 | Update reference ↗ |
| CVE-2026-53517 | 15 Jul 2026 | >= 1.4.8-beta.7, < 1.6.0; >= 1.6.0, < 1.6.11 | 1.6.11. | Update reference ↗ |
| CVE-2026-45337 | 15 Jul 2026 | >= 1.6.0, < 1.6.11 | 1.6.11. | Update reference ↗ |
| CVE-2026-53514 | 15 Jul 2026 | < 1.6.11 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-53515 | 15 Jul 2026 | >= 1.2.10, < 1.6.11 | 1.6.11. | Update reference ↗ |
| CVE-2026-53512 | 15 Jul 2026 | < 1.6.11 | 1.6.11. | Update reference ↗ |
| CVE-2026-53518 | 15 Jul 2026 | >= 1.6.0, < 1.6.11 | 1.6.11. | Update reference ↗ |
| CVE-2026-53513 | 15 Jul 2026 | >= 0.1.0, < 1.6.11 | 1.6.11. | Update reference ↗ |
| CVE-2026-53516 | 15 Jul 2026 | < 1.6.11 | 1.6.11. | Update reference ↗ |
| CVE-2026-45364 | 28 May 2026 | < 1.4.17; >= 1.5.0-beta.1, < 1.5.0-beta.9 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-41427 | 24 Apr 2026 | >= 1.4.8-beta.7, < 1.6.5; >= 1.7.0-beta.0, <= 1.7.0-beta.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-61928 | 9 Oct 2025 | < 1.3.26 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-53535 | 7 Jul 2025 | < 1.2.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27143 | 24 Feb 2025 | < 1.1.20 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-56734 | 30 Dec 2024 | < 1.1.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.