CVE-2026-93710

7.5 HIGHpublic exploit available

Published 2026-09-22 · Updated 2026-09-22

AI risk analysis

Summary: Dancer2 framework has a race condition in its hook execution where dying hooks can cause routes to be incorrectly dispatched even after the response has been halted, leading to unexpected behavior and potential data loss. This occurs when exception handlers halt responses but don't prevent cleanup that discards request data, allowing stale routes to execute.
Exploitability: Exploitation requires crafting a hook that dies during route execution and then halts the response, with the specific timing of cleanup not being properly synchronized with the halt operation, making it moderately difficult to trigger reliably.
Blast radius: The impact is moderate as it primarily affects applications using Dancer2 2.0.0 through 2.1.9 where a dying hook could cause unexpected route execution and data processing, potentially leading to inconsistent application state or data corruption.
Detection: No reliable host or network indicator is derivable from the published description.
Prioritized remediation: Upgrade to Dancer2 version 2.2.0 or later which contains the fix for the hook cleanup and exception handling race condition.

webperlframeworkvulnerability

Analysis generated locally by garnet-coder (no data left the box). AI-assisted — verify against primary sources before acting.

NVD 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.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Weaknesses

CWE-460

Public exploit & PoC references

References

Data: NVD (public domain). Analysis: local $0 model. Defensive use only.