# CVE-2025-40910: Net::IP::LPM version 1.10 for Perl does not properly consider leading zero characters in IP CIDR address strings, which could allow attacker

> Attackers can bypass IP-based access controls by using leading zeros in CIDR strings, confusing octal and decimal parsing in the Net::IP::LPM Perl library.

- **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:** No
- **Published:** 27 Jun 2025
- **Updated:** 7 Sep 2026
- **Also known as:** GHSA-7ffq-hwvw-j35c

## What is CVE-2025-40910?

CVE-2025-40910 is a medium-severity vulnerability, published on 27 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Net::IP::LPM version 1.10 for Perl does not properly consider leading zero characters in IP CIDR address strings, which could allow attackers to bypass access control that is based on IP addresses.

Leading zeros are used to indicate octal numbers, which can confuse users who are intentionally using octal notation, as well as users who believe they are using decimal notation.

Weakness: CWE-1287 (Improper Validation of Specified Type of Input)

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


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

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

## Is CVE-2025-40910 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-40910 is a medium-severity vulnerability, published on 27 Jun 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-40910 in the wild and no public exploit code.

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

## Sources

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

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