# CVE-2026-93709: Dancer2 versions before 2.2.0 for Perl serve a layout as a page when an equivalent spelling of its path misses the guard in the AutoPage handler.

> Attackers can access internal layout files by bypassing path guards in the AutoPage handler, disclosing application structure when auto_page is enabled.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 22 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-93709, GHSA-8fpv-59mj-6jfr, UBUNTU-CVE-2026-93709

## What is CVE-2026-93709?

CVE-2026-93709 is a medium-severity vulnerability, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dancer2 versions before 2.2.0 for Perl serve a layout as a page when an equivalent spelling of its path misses the guard in the AutoPage handler.

The handler compares the request path against the layout directory name as text, while the lookup that follows canonicalises it. A doubled slash, a dot segment, a percent-encoded slash, or a different capitalisation on a case-insensitive filesystem therefore misses the guard.

The handler is off by default, enabled with auto_page. The layout wrapping every page is already public, so this discloses one of the application's other layouts.

Weakness: CWE-41 (Improper Resolution of Path Equivalence)

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


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

Upgrade to a fixed version.

## Is CVE-2026-93709 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93709 is a medium-severity vulnerability, published on 22 Sep 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-2026-93709 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-2026-93709/ (Markdown: https://insights.sbomify.com/CVE-2026-93709/index.md)
```

## Sources

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

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