# CVE-2025-40914: Perl CryptX before version 0.087 contains a dependency that may be susceptible to an integer overflow


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 11 Jun 2025
- **Updated:** 11 Jun 2025
- **Also known as:** AZL-63927, DEBIAN-CVE-2025-40914, UBUNTU-CVE-2025-40914, openSUSE-SU-2025:15259-1

## What is CVE-2025-40914?

CVE-2025-40914 is a critical vulnerability in MIK CryptX, published on 11 Jun 2025. 

### Official 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.

Weakness: CWE-1395 (Dependency on Vulnerable Third-Party Component)

## Which versions are affected by CVE-2025-40914?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-CryptX` | openSUSE:Tumbleweed | All versions | 0.87.0-1.1 |

## How do I fix CVE-2025-40914?

Upgrade to a fixed version.

## Is CVE-2025-40914 being exploited?

There is no known exploitation of CVE-2025-40914 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40914 and fix it if it is affected.

What it is: CVE-2025-40914 is a critical vulnerability in MIK CryptX, published on 11 Jun 2025. 
Exploitation: There is no known exploitation of CVE-2025-40914 in the wild and no public exploit code.

Affected product: MIK CryptX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-40914/ (Markdown: https://insights.sbomify.com/CVE-2025-40914/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-40914
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-40914
- OSV: https://osv.dev/vulnerability/CVE-2025-40914

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-40914/
Summaries are generated and may contain mistakes; the official description above is the record.