Authorization bypass via premature hook cleanup
Published Sep 22, 2026 · Updated Sep 22, 2026
Incorrect authorization in PerlDancer Dancer2 2.0.0 through 2.1.0 allows remote attackers to execute routes rejected by before hooks. Dancer2::Core::App::compile_hooks calls cleanup after a halting exception handler, erasing the halted response before _dispatch_route checks it. The bypass requires an on_hook_exception handler that halts and a before hook that dies; the refused route then runs with its configured side effects.
Summary
What happened
Incorrect authorization in PerlDancer Dancer2 2.0.0 through 2.1.0 allows remote attackers to execute routes rejected by before hooks. Dancer2::Core::App::compile_hooks calls cleanup after a halting exception handler, erasing the halted response before _dispatch_route checks it. The bypass requires an on_hook_exception handler that halts and a before hook that dies; the refused route then runs with its configured side effects.
The record
- CVE
- CVE-2026-93710
- Published
- Sep 22, 2026
- Updated
- Sep 22, 2026
- Vendor
- PerlDancer
- Product
- Dancer2
- Classifications
- CWE-863, CWE-755, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 22, 2026CVE publishedPublication date reported by the CVE source.
- Sep 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <2.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started