# CVE-2025-40913: Net::Dropbear versions through 0.16 for Perl contains a dependency that may be susceptible to an integer overflow

> An integer overflow in the embedded libtommath library within Net::Dropbear can lead to denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jul 2025
- **Updated:** 16 Jul 2025
- **Also known as:** AZL-65547, AZL-65550, AZL-65571, GHSA-x86q-3xjx-wg89

## What is CVE-2025-40913?

CVE-2025-40913 is a medium-severity vulnerability in ATRODO Net::Dropbear, published on 16 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Net::Dropbear versions through 0.16 for Perl contains a dependency that may be susceptible to an integer overflow.

Net::Dropbear 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-40913?


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

Upgrade to a fixed version.

## Is CVE-2025-40913 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-40913 is a medium-severity vulnerability in ATRODO Net::Dropbear, published on 16 Jul 2025. 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-40913 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-40913/ (Markdown: https://insights.sbomify.com/CVE-2025-40913/index.md)
```

## Sources

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

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