CVE-2025-40920: ETHER Catalyst::Authentication::Credential::HTTP · Generation of Predictable Numbers or Identifiers
Affects ETHER Catalyst::Authentication::Credential::HTTPSource CVE Database V5
Not known to be exploited · CVSS 8.6 High.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 11 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ETHER Catalyst::Authentication::Credential::HTTP | Affected
| Fixed in– |
AI-suggested
European organizations should immediately audit their use of Catalyst::Authentication::Credential::HTTP modules to identify affected versions (1.018 and earlier, specifically 0.06). Since no official patches are currently linked, developers should modify the nonce generation code to replace Data::UUID-based version 3 UUIDs with nonces generated from a cryptographically secure random number generator, such as Perl's Crypt::Random or other libraries compliant with RFC 7616. Implementing nonce generation using secure random sources will prevent predictability and strengthen authentication security. Additionally, organizations should monitor their web authentication logs for unusual or repeated nonce values that could indicate attempted exploitation. Applying strict access controls and network segmentation around affected services can reduce exposure. Finally, maintain vigilance for vendor updates or patches and apply them promptly once available. Incorporating security code reviews focusing on cryptographic practices in authentication modules is recommended to prevent similar issues.
Description
Catalyst::Authentication::Credential::HTTP versions 1.018 and earlier for Perl generate nonces using the Perl Data::UUID library. * Data::UUID does not use a strong cryptographic source for generating UUIDs. * Data::UUID returns v3 UUIDs, which are generated from known information and are unsuitable for security, as per RFC 9562. * The nonces should be generated from a strong cryptographic source, as per RFC 7616.
References
- security.metacpan.org/patches/C/Catalyst-Authentication-Credential-HTTP/1.018/CVE-2025-40920-r1.patch (opens in a new tab)
- github.com/perl-catalyst/Catalyst-Authentication-Credential-HTTP/pull/1 (opens in a new tab)
- metacpan.org/release/ETHER/Catalyst-Authentication-Credential-HTTP-1.018/source/lib/Catalyst/Authentication/Credential/HTTP.pm (opens in a new tab)
- datatracker.ietf.org/doc/html/rfc9562 (opens in a new tab)
- datatracker.ietf.org/doc/html/rfc7616 (opens in a new tab)
- github.com/perl-catalyst/Catalyst-Authentication-Credential-HTTP/commit/ad2c03aad95406db4ce35dfb670664ebde004c18 (opens in a new tab)
- openwall.com/lists/oss-security/2025/08/12/1 (opens in a new tab)