CVE-2025-25298: Missing Maximum Password Length Validation in Strapi Password Hashing

Severity: medium (CVSS 5.3 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.4% probability of exploitation in the next 30 days
Public exploit or detection template: yes
Published: 2025-10-16 · updated 2026-10-19
Weakness: CWE-261

Description

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.

Affected products

strapi: before 5.10.3 — fixed in 5.10.3

How to fix

Upgrade to a fixed version: strapi 5.10.3. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2025-25298 or the next vulnerability affects your stack