# CVE-2026-95811: Lemonldap::NG::Handler versions from 2.0.0 before 2.16.10, from 2.17.0 before 2.21.6, from 2.22.0 before 2.23.4 for Perl allow an equivalent

> Authenticated users can bypass locationRules restrictions via path normalization mismatches, accessing resources if the default rule is permissive.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 26 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-95811, GHSA-3rh3-f3vh-mgjh, UBUNTU-CVE-2026-95811

## What is CVE-2026-95811?

CVE-2026-95811 is a medium-severity authentication bypass vulnerability, published on 25 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Lemonldap::NG::Handler versions from 2.0.0 before 2.16.10, from 2.17.0 before 2.21.6, from 2.22.0 before 2.23.4 for Perl allow an equivalent spelling of a path to bypass the locationRules that restrict it.

The handler matches each vhost's locationRules regular expressions against REQUEST_URI, the raw request line, while the web server routes on the path it has already percent-decoded and normalized. A request that percent-encodes a character of the path, inserts dot segments, or doubles a slash therefore reaches the protected resource under a URI that no rule regexp matches, and the vhost's default rule decides access. Deny rules, identity and group conditions, and unprotect and skip rules are bypassed alike.

Only a vhost whose default rule is more permissive than its other rules is affected. An authenticated user then reaches any URL a locationRules regexp was meant to restrict, but gains no more than that default rule already grants.

Weakness: CWE-863 (Incorrect Authorization), CWE-180 (Incorrect Behavior Order: Validate Before Canonicalize)

## Which versions are affected by CVE-2026-95811?


## How do I fix CVE-2026-95811?

Upgrade to a fixed version.

## Is CVE-2026-95811 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-95811 and fix it if it is affected.

What it is: CVE-2026-95811 is a medium-severity authentication bypass vulnerability, published on 25 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-95811 exists.

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

## Sources

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

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