# CVE-2025-59518: Command injection in LemonLDAP::NG

> Administrators can execute arbitrary OS commands on the server via the Safe jail due to improper localization of underscores during rule evaluation.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2025
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2025-59518, GHSA-fxqv-qm7m-363x, UBUNTU-CVE-2025-59518

## What is CVE-2025-59518?

CVE-2025-59518 is a high-severity command injection vulnerability in lemonldap-ng LemonLDAP::NG, published on 17 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In LemonLDAP::NG before 2.16.7 and 2.17 through 2.21 before 2.21.3, OS command injection can occur in the Safe jail. It does not Localize _ during rule evaluation. Thus, an administrator who can edit a rule evaluated by the Safe jail can execute commands on the server.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

Upgrade to a fixed version.

## Is CVE-2025-59518 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59518 is a high-severity command injection vulnerability in lemonldap-ng LemonLDAP::NG, published on 17 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59518 in the wild and no public exploit code.

Affected product: lemonldap-ng LemonLDAP::NG. 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-59518/ (Markdown: https://insights.sbomify.com/CVE-2025-59518/index.md)
```

## Sources

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

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