CVE-2026-41564VulnerabilityPublished 10 Jun 2026Updated 17 Sep 2026

SUSE · Security update for perl-CryptX

Affects SUSESource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2026-41565

Authoritative record:CVE-2026-41564· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade SUSE CryptX to 0.088 soon.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.088

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 23 Apr 2026
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

Upgrade CryptX to 0.088.

Affected software

Product	Affected	Fixed in
MIKCryptX	Affected <0.088	Fixed in 0.088
GitHubCryptX`pkg:github/CryptX`Other threats	Affected <0.088	Fixed in 0.088

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A security update to perl-CryptX version 0.89.0 is available and should be applied to remediate the vulnerabilities CVE-2026-41564 and CVE-2026-41565. Users should upgrade to this version or later to ensure the security fixes and improvements are in place. No additional mitigation steps are indicated by the vendor advisory.

Description

This security update for perl-CryptX addresses multiple issues including security and hardening fixes across various cryptographic modules. It includes fixes for CVE-2026-41564 and CVE-2026-41565, updates to cryptographic algorithms and functions, and improvements in documentation and compliance with cryptographic standards. The update is version 0.89.0 and includes bundled updates to libtomcrypt and libtommath libraries.

Impact

The vulnerabilities fixed by this update could potentially affect the security and integrity of cryptographic operations performed by perl-CryptX. The update mitigates these risks by applying security and hardening fixes, improving cryptographic lifecycle management, and updating underlying cryptographic libraries. No known exploits in the wild have been reported for these CVEs at the time of publication.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats