CVE-2025-25298
- Source
- https://cve.org/CVERecord?id=CVE-2025-25298
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-25298.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2025-25298
- Aliases
- Published
- 2025-10-16T16:21:45.585Z
- Modified
- 2026-04-10T05:23:14.972371Z
- Severity
-
- 6.3 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N CVSS Calculator
- Summary
- Missing Maximum Password Length Validation in Strapi Password Hashing
- Details
-
Strapi is an open source headless CMS. The @strapi/core package before version 5.10.3 does not enforce a maximum password length when using bcryptjs for password hashing. Bcryptjs ignores any bytes beyond 72, so passwords longer than 72 bytes are silently truncated. A user can create an account with a password exceeding 72 bytes and later authenticate with only the first 72 bytes. This reduces the effective entropy of overlong passwords and may mislead users who believe characters beyond 72 bytes are required, creating a low likelihood of unintended authentication if an attacker can obtain or guess the truncated portion. Long over‑length inputs can also impose unnecessary processing overhead. The issue is fixed in version 5.10.3. No known workarounds exist.
- Database specific
{ "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-261" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/25xxx/CVE-2025-25298.json" }- References
Affected packages
Git / github.com/strapi/strapi
Affected ranges
- Type
- GIT
- Repo
- https://github.com/strapi/strapi
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixed