Quick answers
- Is CVE-2026-121448 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121448 being exploited in the wild.
- How severe is CVE-2026-121448?
- High severity, with a CVSS score of 8.3, published 3 November 2026.
- Which products and versions are affected?
- Finsys Dockhand before 1.0.54.
- Is there a fix for CVE-2026-121448?
- Yes: fixed in 1.0.54. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-121448 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-121448?
- 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: 1.0.54
Technical details
The vulnerability stems from double-decoding of stack names in the environment routes (/api/stacks/[name]/env/raw and related endpoints) without the path containment checks applied elsewhere in the codebase. An authenticated attacker sending a double-encoded payload like %252e%252e decodes to .. by the time it reaches the path join operation, allowing traversal outside the stacks root. The write primitive can poison .env files used in deployments, and the read primitive discloses cross-environment secrets; an RBAC bypass also allows users to access other environments' files.
Affected products
- Finsys Dockhand before 1.0.54
Timeline
- 2026-10-19: disclosed
- 2026-11-03: advisory