Quick answers
- Is CVE-2026-110130 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110130 being exploited in the wild.
- How severe is CVE-2026-110130?
- Critical severity, with a CVSS score of 10, published 13 October 2026.
- Which products and versions are affected?
- Finsys Dockhand before 1.0.45.
- Is there a fix for CVE-2026-110130?
- Yes: fixed in v1.0.45. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110130 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-110130?
- Check whether you run Finsys Dockhand at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: v1.0.45
Technical details
Two chained bugs create an authentication bypass: (1) the global auth hook contains a static-asset check that exits early for any path ending in .js, .css, .png, .svg, .ico, .webp, or .jpg—including /api/* routes—bypassing all session validation; (2) user-mutation handlers perform fail-open authorization checks that skip permission gates when auth.user is null, allowing an unauthenticated caller to modify any user record. An attacker sends an unauthenticated PUT request to /api/users/1.js with a new password JSON payload, which reaches the handler with id="1.js" (parsed to integer 1, the admin), and the missing authentication check allows the password update to succeed.
Affected products
- Finsys Dockhand before 1.0.45
Timeline
- 2026-08-27: disclosed
- 2026-10-13: advisory