# CVE-2025-40912: CryptX for Perl before version 0.065 contains a dependency that may be susceptible to malformed unicode

> A dependency in the Perl CryptX library is susceptible to malformed unicode issues, potentially causing denial of service.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jun 2025
- **Updated:** 11 Jun 2025
- **Also known as:** DEBIAN-CVE-2025-40912, GHSA-w3qg-5chj-8g9g, UBUNTU-CVE-2025-40912

## What is CVE-2025-40912?

CVE-2025-40912 is a critical vulnerability in MIK CryptX, published on 11 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CryptX for Perl before version 0.065 contains a dependency that may be susceptible to malformed unicode.

CryptX embeds the tomcrypt library. The versions of that library in CryptX before 0.065 may be susceptible to CVE-2019-17362.

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

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


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

Upgrade to a fixed version.

## Is CVE-2025-40912 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-40912 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-40912 is a critical vulnerability in MIK CryptX, published on 11 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-40912 exists.

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-40912/ (Markdown: https://insights.sbomify.com/CVE-2025-40912/index.md)
```

## Sources

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

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