Skip to main content
Vulnerability Database/CVE-2026-111443

CVE-2026-111443: Wheels Framework Auth Bypass Vulnerability

CVE-2026-111443 is an authentication bypass flaw in Wheels Framework versions 4.0.6 through 4.1.2 that allows unauthenticated clients to switch request contexts. This post explains its impact, affected versions, and mitigation steps.

Published:

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-111443 Overview

CVE-2026-111443 affects the Wheels framework versions 4.0.6 through 4.1.2. An unauthenticated remote client can force a request to execute in a separate test application context, including on production deployments. The switch triggers through any of three vectors: an X-Wheels-Test-Context HTTP header with any value, a WHEELS_TEST_CONTEXT cookie, or a test-runner path substring appearing anywhere in the request URL, including the query string. The alternate application shares configuration, environment, datasource, and debug settings with the primary context, so this is not an authentication bypass or data escalation. The flaw is tracked as [CWE-348: Use of Less Trusted Source] and is fixed in Wheels 4.2.0.

Critical Impact

Remote unauthenticated attackers can bypass runtime-enabled maintenance mode, create a parallel in-memory rate-limit counter set, and force additional application-startup side effects that consume memory.

Affected Products

  • Wheels 4.0.6
  • Wheels 4.0.7 through 4.1.1
  • Wheels 4.1.2

Discovery Timeline

  • 2026-10-16 - CVE-2026-111443 published to NVD
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-111443

Vulnerability Analysis

The Wheels framework exposes an internal test-application context intended for development and automated test harnesses. In vulnerable releases, the request router treats client-supplied inputs as authoritative signals for selecting that context. Any of three untrusted inputs will cause the switch: the X-Wheels-Test-Context header, the WHEELS_TEST_CONTEXT cookie, or a test-runner path fragment appearing anywhere in the URL, including the query string.

The alternate context inherits the primary application's configuration, environment, datasource, and debug flags. There is no privilege gain and no new data exposure. The impact is instead operational. The alternate context runs its own startup lifecycle, allocates its own in-memory structures, and maintains its own rate-limit counters. An attacker who can reach the application over the network can force these side effects at will.

Root Cause

The router trusts client-controlled headers, cookies, and URL path fragments to select an application context. This matches [CWE-348: Use of Less Trusted Source], where a trust decision is made based on data an attacker fully controls. No signed token, server-side session, or environment check gates the switch.

Attack Vector

Exploitation requires only network reach to a vulnerable Wheels application. The attacker issues standard HTTP requests that include one of the three triggers. For example, adding X-Wheels-Test-Context: 1 to any request, setting the WHEELS_TEST_CONTEXT cookie, or appending the test-runner path substring to the query string will route the request into the test context. Repeated requests multiply the memory and startup overhead. The parallel rate-limit counter set means policies enforced in the primary context do not throttle requests in the alternate context, enabling abuse scenarios that assume per-source request budgets.

See the GitHub Security Advisory GHSA-xcj9-wm25-4cg4 for upstream technical details.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-111443

Indicators of Compromise

  • Inbound HTTP requests containing the X-Wheels-Test-Context header on production hostnames.
  • Requests carrying a WHEELS_TEST_CONTEXT cookie on any endpoint.
  • URLs containing the Wheels test-runner path substring in the path or query string on production applications.
  • Unexpected growth in application process memory correlated with repeated test-context requests.

Detection Strategies

  • Inspect web server, load balancer, and WAF logs for the header and cookie names associated with this vulnerability.
  • Alert on any request to production hostnames whose URL contains the Wheels test-runner path fragment.
  • Correlate maintenance-mode activations with subsequent successful request traffic to detect bypass attempts.

Monitoring Recommendations

  • Baseline memory and startup counters per Wheels application instance and alert on deviations.
  • Track rate-limit counter cardinality to identify a second counter set appearing in memory.
  • Forward application logs to a central analytics platform and build queries for the specific trigger strings referenced above.

How to Mitigate CVE-2026-111443

Immediate Actions Required

  • Upgrade Wheels to version 4.2.0 or later on all production and staging deployments.
  • Block or strip the X-Wheels-Test-Context header and WHEELS_TEST_CONTEXT cookie at the reverse proxy or WAF until patching is complete.
  • Reject requests whose URL contains the Wheels test-runner path fragment at the edge for production hostnames.

Patch Information

The Wheels maintainers fixed this issue in version 4.2.0. The patched release removes client control over test-context selection. Refer to the GitHub Security Advisory GHSA-xcj9-wm25-4cg4 for release notes and upgrade guidance.

Workarounds

  • Configure the upstream reverse proxy or WAF to drop the X-Wheels-Test-Context header on all inbound requests.
  • Drop or rewrite the WHEELS_TEST_CONTEXT cookie before requests reach the application.
  • Deny requests where the URL path or query string contains the Wheels test-runner path substring on production hostnames.
  • Enforce maintenance mode at the load balancer rather than only at application runtime, since runtime-only maintenance mode can be bypassed through the alternate context.

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.