CVE-2025-40918VulnerabilityPublished 9 Apr 2026Updated 17 Sep 2026

SUSE · Security update for perl-Authen-SASL

Affects SUSESource GCVE Database

Compare

Authoritative record:CVE-2025-40918· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% 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:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 31 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SUSE Product Security Team SUSE	Affected SUSE aarch64 perl-Crypt-URandom-0.550.0-160000.1.1.aarch64 noarch perl-Authen-SASL-2.170.0-160000.3.1.noarch perl-Crypt-URandom-0:0.550.0-160000.1.1.aarch64 perl-Authen-SASL-0:2.170.0-160000.3.1.noarch	Fixed in–

AI-suggested

A security update is available that fixes the vulnerability by using Crypt::URandom for nonce generation. Users should apply the update provided by the SUSE Product Security Team to remediate this issue. No additional mitigation steps are indicated.

Description

A security update for perl-Authen-SASL addresses CVE-2025-40918 by changing nonce generation to use Crypt::URandom. This update fixes a vulnerability related to nonce generation in the perl-Authen-SASL module. No specific affected versions are stated. The severity is assessed as medium.

Impact

The vulnerability relates to nonce generation in perl-Authen-SASL, which could affect the security of authentication processes relying on this module. The medium severity suggests a moderate impact on confidentiality or integrity, but no active exploits are known. The update improves nonce randomness and security.

Summary

The perl-Authen-SASL module had a vulnerability identified as CVE-2025-40918, which involved the method of generating nonces. The update replaces the nonce generation mechanism to use Crypt::URandom, improving the security of nonce creation. This change mitigates the vulnerability described in bsc#1246623. No further technical details or CVSS score are provided.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Sep 2026, 02:29 UTC

Technical details

References

Community reviews

Related threats