CVE-2026-111446
8.6HighPublished 16 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Impact
- High impact on confidentiality
- Weakness
- CWE-863
Impact
Unauthenticated remote attackers can read environment secrets, database configurations, and trigger test runs that may alter primary database records. They only need network access to the application endpoints under /wheels/*.
Root cause
Development tools under /wheels/* either lacked access controls or relied on client-supplied headers instead of verifying the connecting peer address.
Affected systems
Wheels 4.0.0 through 4.1.2
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
Fix & remediation
Upgrade Wheels to 4.2.0. If upgrading immediately is not possible, block remote access to the /wheels/* path or ensure enablePublicComponent is set to false in your configuration.
$ box install wheels@4.2.0AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
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.