Vulnerability in Wheels CLI (CVE-2026-110909)
Summary
Vulnerability in Wheels CLI (CVE-2026-110909). Confidential information can be exposed externally. Mitigation: upgrade to 4.1.1 or later.
Original description
The description as published by the source.
Wheels CLI through 4.1.0 does not verify that the local development server answering its HTTP requests belongs to the current project. A process listening on a port targeted by the CLI can receive the project's reload password and code submitted through wheels reload or wheels console; console also probes common ports when the project server is down. Other commands can perform unintended state-changing operations against a different local application's server and database. Exploitation requires a process listening on a targeted local port and the developer running an affected command. This is fixed in 4.1.1, including changes to the CLI and application template.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-110909 has been found in Wheels CLI.
Confidential information can be exposed externally. CVSS score: 5.0/10.
What to do: upgrade Wheels CLI to 4.1.1 or later.
If unsure, ask your IT team or search "Wheels CLI CVE-2026-110909" on the vendor's site.
CVE-2026-110909 (Wheels CLI) — CWE-923 / CVSS v3 5.0
Attack vector: local
Patched: 4.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-923) exists in Wheels CLI.
Check the vendor advisory for the affected versions of Wheels CLI.
Severity: Medium (CVSS 5.0/10). Confidential information can be exposed externally.
Update to 4.1.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Wheels CLI を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Wheels CLI to 4.1.1ステージング環境で 4.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web cve@mitre.org
- web nvd.nist.gov
- web github.com