# CVE-2026-93710: Dancer2 versions from 2.0.0 before 2.2.0 for Perl dispatch a route that a dying hook refused when the exception handler halts the response in compile_hooks.

> Attackers can bypass security checks in Dancer2 hooks, causing refused routes to execute and modify data despite intended blocks.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 22 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-93710, GHSA-qp5m-r6hx-rjhj, GHSA-v527-r4px-7vx7, UBUNTU-CVE-2026-93710

## What is CVE-2026-93710?

CVE-2026-93710 is a high-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 from 2.0.0 before 2.2.0 for Perl dispatch a route that a dying hook refused when the exception handler halts the response in compile_hooks.

A hook that dies fires core.app.hook_exception, then calls cleanup unless the failing hook is the exception handler. A handler that halts does not stop that cleanup, which discards the request, response and session the dispatcher has yet to read, so the refused route runs.

The handler has to halt the response object by calling its halt method or setting is_halted: the halt keyword unwinds through with_return before cleanup runs.

A check in a before hook is not enforced: the caller gets the refusal, while the route body runs and its writes land.

Weakness: CWE-460 (Improper Cleanup on Thrown Exception)

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


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

Upgrade to a fixed version.

## Is CVE-2026-93710 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93710 is a high-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-93710 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-93710/ (Markdown: https://insights.sbomify.com/CVE-2026-93710/index.md)
```

## Sources

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

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