CVE-2026-110909: Wheels CLI insufficient server verification in HTTP requests

CVE-2026-110909 · Severity: medium · CVSS 5 · Published 2026-10-15

Wheels CLI is a development tool that developers use to manage local project servers. Through version 4.1.0, the CLI fails to verify it is communicating with the correct project's server, allowing a different application listening on the same local port to receive sensitive credentials (a reload password) and execute arbitrary code or state-changing commands against unintended databases. An attacker would need to run a malicious process on the same machine as the developer and have the developer run affected CLI commands.

Vendors: Wheels.

Quick answers

Is CVE-2026-110909 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-110909 being exploited in the wild.
How severe is CVE-2026-110909?
Medium severity, with a CVSS score of 5, published 15 October 2026.
Which products and versions are affected?
Wheels CLI through 4.1.0.
Is there a fix for CVE-2026-110909?
Yes: fixed in Wheels CLI 4.1.1. Until then: Until upgraded, assign each project a unique port in lucee.json and avoid running other servers on that port. Before running state-changing CLI commands, stop other local development servers. Avoid wheels console and wheels reload on machines where other users run servers.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-09-28"},{"kind":"advisory","at":"2026-10-15"},{"kind":"patched","at":"2026-10-15","note":"Wheels 4.1.1 released"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-110909 attacked?
It is attacked with local access, in a software library.
Am I affected by CVE-2026-110909?
Check whether you run Wheels CLI 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: Wheels CLI 4.1.1

Until upgraded, assign each project a unique port in lucee.json and avoid running other servers on that port. Before running state-changing CLI commands, stop other local development servers. Avoid wheels console and wheels reload on machines where other users run servers.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-09-28"},{"kind":"advisory","at":"2026-10-15"},{"kind":"patched","at":"2026-10-15","note":"Wheels 4.1.1 released"}]

Technical details

Wheels CLI sends HTTP requests to a local development server (default port 8080) without verifying that the server is the intended project's own instance. The vulnerability allows credential leakage via URL query string (the reload password), arbitrary code evaluation (wheels console), and unintended state changes (migrate, seed, db reset, jobs work commands) when a different process listens on the target port. Exploitation requires a malicious process listening on a local port and the developer executing an affected command; no remote network access is needed. Fixed in 4.1.1 by implementing process verification via OS socket inspection and moving the password to HTTP headers.

Affected products

  • Wheels Wheels CLI through 4.1.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.