Authorization Flaw in Wheels (CVE-2026-111446)
Summary
Vulnerability in Wheels (CVE-2026-111446). Confidential information can be exposed externally. Mitigation: upgrade to 4.2.0 or later.
Original description
The description as published by the source.
Wheels 4.0.0 through 4.1.2 exposes password-less development tools under /wheels/* to remote clients when enablePublicComponent=true, as it is by default in development. Before 4.1.2 these tools have no local-access restriction; in 4.1.2 the restriction trusts client-supplied headers without checking the connecting peer. Remote clients can obtain application settings, environment/datasource details and routes, and start test runs. Where application tests use the primary datasource, those runs can write to the real application database. The separately protected migrator and CLI endpoints are not affected. This is fixed in 4.2.0.
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-111446 has been found in Wheels.
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: upgrade Wheels to 4.2.0 or later.
If unsure, ask your IT team or search "Wheels CVE-2026-111446" on the vendor's site.
CVE-2026-111446 (Wheels) — CWE-863 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.2.0 — 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.
Incorrect authorization (CWE-863) exists in Wheels.
Check the vendor advisory for the affected versions of Wheels.
Severity: High (CVSS 8.6/10). Confidential information can be exposed externally.
Update to 4.2.0.
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. Run grep -r 'Wheels' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Wheels' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Wheelsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Wheels to 4.2.0ステージング環境で 4.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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