Skip to main content
VulnerabilityPublished

CVE-2025-40914: MIK CryptX · Dependency on Vulnerable Third-Party Component

Affects MIK CryptXSource CVE Database V5

0

Mentioned vulnerabilities

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% 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:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
MIK CryptXAffected
  • =0.002
Fixed in–

AI-suggested

Immediate mitigation should focus on upgrading CryptX to version 0.087 or later, where the vulnerable libtommath dependency has been addressed. If upgrading is not immediately feasible, organizations should audit their Perl applications to identify usage of CryptX and assess exposure. Employing runtime application self-protection (RASP) or intrusion detection systems (IDS) to monitor for anomalous behaviors indicative of exploitation attempts can provide interim defense. Additionally, organizations should implement strict network segmentation and firewall rules to limit external access to services using CryptX. Code review and static analysis tools should be used to detect and remediate any unsafe integer operations in custom cryptographic code. Given the dependency nature of the vulnerability, supply chain security practices should be enhanced, including verifying the integrity and versions of third-party libraries. Finally, organizations should stay alert for patches or advisories from the vendor and subscribe to vulnerability intelligence feeds to respond promptly to emerging exploit information.

Description

Perl CryptX before version 0.087 contains a dependency that may be susceptible to an integer overflow. CryptX embeds a version of the libtommath library that is susceptible to an integer overflow associated with CVE-2023-36328.

References

Community reviews

Loading reviews…