# CVE-2025-15638: Net::Dropbear versions before 0.14 for Perl contains a vulnerable version of libtomcrypt

> Net::Dropbear bundles vulnerable libtomcrypt versions, allowing attackers to exploit underlying cryptographic flaws for code execution or denial of service.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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:** No
- **Published:** 21 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** GHSA-fwph-xhj4-v8r5

## What is CVE-2025-15638?

CVE-2025-15638 is a critical vulnerability in ATRODO Net::Dropbear, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Net::Dropbear versions before 0.14 for Perl contains a vulnerable version of libtomcrypt.

Net::Dropbear versions before 0.14 includes versions of Dropbear 2019.78 or earlier. These include versions of libtomcrypt v1.18.1 or earlier, which is affected by CVE-2016-6129 and CVE-2018-12437.

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

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

It affects 1 product.


Products: Atrodo Net\.

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

No fix has been published for CVE-2025-15638 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-15638 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15638 is a critical vulnerability in ATRODO Net::Dropbear, published on 21 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-15638 in the wild and no public exploit code.

Affected product: ATRODO Net::Dropbear. 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-15638/ (Markdown: https://insights.sbomify.com/CVE-2025-15638/index.md)
```

## Sources

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

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