Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-111446 Overview
CVE-2026-111446 affects the Wheels framework versions 4.0.0 through 4.1.2, exposing password-less development tools under the /wheels/* path to remote clients. The tools are reachable when enablePublicComponent=true, which is the default configuration in development mode. Remote attackers can retrieve application settings, environment and datasource details, and defined routes without authentication. Attackers can also initiate test runs, which may write to the production database when application tests reuse the primary datasource. The flaw is classified under CWE-863: Incorrect Authorization and is fixed in Wheels 4.2.0.
Critical Impact
Unauthenticated remote clients can read application configuration and trigger test runs that write to the real application database.
Affected Products
- Wheels 4.0.0 through 4.1.1 (no local-access restriction on /wheels/*)
- Wheels 4.1.2 (restriction present but trusts client-supplied headers)
- Any Wheels deployment running with enablePublicComponent=true
Discovery Timeline
- 2026-10-16 - CVE-2026-111446 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-111446
Vulnerability Analysis
The Wheels framework exposes a set of development utilities under the /wheels/* route group. These tools include endpoints for inspecting application settings, environment variables, datasource configuration, and the application route table, as well as endpoints that trigger test suite execution. In versions prior to 4.1.2, the framework applies no restriction limiting these endpoints to local clients. Any remote client that can reach the HTTP listener receives full access.
Version 4.1.2 introduced a local-access check, but the check derives the client address from request headers such as X-Forwarded-For rather than from the connecting peer address. An attacker supplies a header value that spoofs a loopback origin and bypasses the restriction. The separately protected migrator and CLI endpoints enforce their own authorization and are not affected.
The highest-impact action is starting a test run. When application tests are configured to use the primary datasource rather than an isolated test datasource, the test harness writes to and may truncate production data.
Root Cause
The root cause is incorrect authorization [CWE-863]. The access control logic trusts attacker-controllable HTTP headers to determine whether a request originates locally. The connecting peer address is never validated against the loopback range before granting access to privileged diagnostics and test-execution routes.
Attack Vector
An attacker sends an HTTP request directly to a /wheels/* endpoint over the network. No credentials, user interaction, or prior access are required. On 4.1.2 deployments, the attacker adds a spoofed header indicating a loopback source address to bypass the local-only check. The attacker then retrieves configuration data or issues a request that invokes the test runner against the primary datasource.
The security advisory describes the exposed endpoints and the header-trust flaw. See the GitHub Security Advisory GHSA-6v6c-p375-vxw9 for the authoritative technical description.
Detection Methods for CVE-2026-111446
Indicators of Compromise
- HTTP requests to paths matching /wheels/* from non-loopback source addresses in access logs
- Requests to /wheels/* containing X-Forwarded-For, X-Real-IP, or similar headers claiming a 127.0.0.1 origin from external clients
- Unexpected test-runner invocations or schema changes against the primary application database
- Outbound reconnaissance patterns enumerating framework-specific URLs on internet-exposed hosts
Detection Strategies
- Alert on any external access to /wheels/* routes in reverse proxy or application access logs
- Correlate web server logs with database audit logs to identify test-driven writes to production tables
- Flag HTTP requests where a loopback-claiming forwarded header arrives from a non-local socket
Monitoring Recommendations
- Monitor Wheels application logs for diagnostic endpoint hits and test-runner start events
- Track outbound exposure of ColdFusion and Wheels applications using asset inventory and external attack surface tools
- Review database change logs for schema or row-level modifications that correlate with HTTP traffic to /wheels/*
How to Mitigate CVE-2026-111446
Immediate Actions Required
- Upgrade Wheels to version 4.2.0 or later, which fixes the authorization flaw
- Set enablePublicComponent=false in any environment reachable from untrusted networks
- Block external access to /wheels/* paths at the reverse proxy or web application firewall
- Verify that test environments use a dedicated datasource separate from production
Patch Information
The fix is included in Wheels 4.2.0. The patched release removes trust in client-supplied headers and enforces local-only access using the connecting peer address. Refer to the GitHub Security Advisory GHSA-6v6c-p375-vxw9 for release notes and remediation details.
Workarounds
- Disable the public component by setting enablePublicComponent=false in the application configuration
- Deny /wheels/* paths at the ingress layer for all source addresses that are not explicitly on the loopback interface
- Reconfigure application tests to point at an isolated datasource, ensuring test runs cannot touch production data
- Bind the application HTTP listener to 127.0.0.1 in development environments to prevent remote reachability
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

