Vulnerability in Wheels (CVE-2026-111443)
Summary
Vulnerability in Wheels (CVE-2026-111443). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.2.0 or later.
Original description
The description as published by the source.
Wheels 4.0.6 through 4.1.2 lets an unauthenticated client switch a request into a separate test application context, including in production, by supplying an X-Wheels-Test-Context header or WHEELS_TEST_CONTEXT cookie with any value, or including a test-runner path anywhere in the URL, even the query string. The alternate application uses the same configuration, environment, datasource and debug settings: this is not an authentication bypass or data/debug escalation. It can bypass maintenance mode enabled only at runtime, provide a second set of in-memory rate-limit counters, and trigger additional application-startup side effects and memory use. 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-111443 has been found in Wheels.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade Wheels to 4.2.0 or later.
If unsure, ask your IT team or search "Wheels CVE-2026-111443" on the vendor's site.
CVE-2026-111443 (Wheels) — CWE-348 / CVSS v3 6.5
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.
A vulnerability (CWE-348) exists in Wheels.
Check the vendor advisory for the affected versions of Wheels.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
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