Quick answers
- Is CVE-2026-45701 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45701 being exploited in the wild.
- How severe is CVE-2026-45701?
- Medium severity, with a CVSS score of 4, published 1 June 2026.
- Which products and versions are affected?
- sulu/sulu (Packagist) ECOSYSTEM:introduced=3.0.0-alpha1,fixed=3.0.6; Sulu < 2.6.23, < 3.0.6, <= 2.6.22, >= 3.0.0-alpha1, <= 3.0.5.
- Is there a fix for CVE-2026-45701?
- Yes. sulu/sulu (Packagist): upgrade to 3.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45701 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45701?
- Check whether you run sulu/sulu (Packagist) or Sulu at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- sulu/sulu (Packagist): upgrade to 3.0.6 or later
composer require sulu/sulu:^3.0.6
Technical details
Sulu CMS is vulnerable to the use of a broken or risky cryptographic algorithm (CWE-327) within its SecurityBundle. Specifically, the components responsible for generating password reset tokens and API keys utilize a weak hashing mechanism rather than cryptographically secure pseudo-random generators. An unauthenticated remote attacker could potentially predict these tokens or keys, leading to account takeover or unauthorized API access. The vulnerability is located in User.php and ResettingController.php. This issue is resolved in versions 2.6.23 and 3.0.6.
Affected products
- Sulu Sulu < 2.6.23, < 3.0.6
Identifiers
- CVE-2026-45701
- GHSA-7fv8-6pp7-6h85
Timeline
- 2026-05-04: patched: Versions 2.6.23 and 3.0.6 released.
- 2026-05-12: advisory: GitHub Security Advisory GHSA-7fv8-6pp7-6h85 published.
- 2026-06-01: disclosed: CVE-2026-45701 published to NVD.