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

CVE-2026-111721: Open WES Auth Bypass Vulnerability

CVE-2026-111721 is an authorization bypass flaw in Open WES that allows authenticated users to modify stock records across warehouses. 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-111721 Overview

CVE-2026-111721 is an authorization bypass vulnerability in Open WES through version 1.0.0. The flaw resides in the GlobalGatewayFilter component, which fails to enforce auth_warehouse scoping on authenticated requests. Any authenticated user holding the relevant menu permission can enumerate sequential object identifiers against the freezeContainerStock and unfreezeContainerStock endpoints. This allows attackers to modify stock records belonging to warehouses outside their assigned scope. The weakness is categorized as [CWE-639] Authorization Bypass Through User-Controlled Key.

Critical Impact

Authenticated users can freeze or unfreeze container stock in warehouses they do not own, disrupting inventory operations across multi-tenant deployments.

Affected Products

  • Open WES through version 1.0.0
  • modules-gateway/gateway-core component containing GlobalGatewayFilter
  • wes-stock module exposing ContainerStockController endpoints

Discovery Timeline

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

Technical Details for CVE-2026-111721

Vulnerability Analysis

Open WES is a warehouse execution system that enforces multi-warehouse separation through an auth_warehouse attribute attached to user sessions. The GlobalGatewayFilter class is responsible for inspecting inbound API requests at the gateway tier and applying warehouse scoping before routing them to downstream services. The filter authenticates the request and checks menu-level permissions but omits any comparison between the resource owner's warehouse identifier and the caller's auth_warehouse value. Downstream controllers trust the gateway and skip their own scoping checks.

As a result, horizontal privilege escalation is possible across tenants that share the same deployment. An authenticated operator with the stock-freeze menu permission in Warehouse A can target records belonging to Warehouse B simply by changing the numeric identifier submitted to the controller.

Root Cause

The root cause is missing authorization logic between lines 86 and 128 of GlobalGatewayFilter.java. The filter resolves the authenticated principal and verifies menu permissions, but it does not retrieve the target resource's warehouse context nor compare it to the session's auth_warehouse claim. The ContainerStockController endpoints at lines 24 through 34 accept the identifier directly from the client without re-validating ownership.

Attack Vector

Exploitation requires network access to the Open WES gateway and a valid account with the container stock menu permission. The attacker iterates through sequential container stock identifiers and issues POST requests to the freezeContainerStock or unfreezeContainerStock endpoints. Because warehouse ownership is never evaluated, each request succeeds against cross-tenant records. No user interaction is required, and the complexity is low.

See the VulnCheck Security Advisory on Access Control and the HackMD Analysis on Missing Authorization for exploitation walkthroughs.

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-111721

Indicators of Compromise

  • Sequential enumeration of integer identifiers against /freezeContainerStock or /unfreezeContainerStock endpoints from a single authenticated session.
  • Stock state transitions on container records that do not match the acting user's assigned warehouse.
  • High-volume POST requests to container stock endpoints originating from accounts that typically operate in a single warehouse scope.

Detection Strategies

  • Correlate application audit logs with the auth_warehouse claim and alert when the modified record's warehouse differs from the caller's assigned warehouse.
  • Deploy gateway-level request inspection to flag enumeration patterns such as monotonically increasing identifiers.
  • Baseline normal freeze and unfreeze operation volumes per user and alert on deviations.

Monitoring Recommendations

  • Enable verbose logging on the GlobalGatewayFilter and ContainerStockController classes to capture caller identity, target identifier, and resolved warehouse.
  • Forward Open WES application logs to a centralized SIEM and build correlation rules joining user warehouse scope with modified record metadata.
  • Review database audit trails for stock state changes attributed to users outside the record's owning warehouse.

How to Mitigate CVE-2026-111721

Immediate Actions Required

  • Restrict access to the container stock menu permission to trusted operators until a patched release is available.
  • Deploy a reverse proxy or Web Application Firewall rule that enforces warehouse scoping based on session claims before requests reach the Open WES gateway.
  • Audit historical application logs for prior cross-warehouse stock modifications and reconcile inventory records.

Patch Information

No vendor patch is referenced in the published advisory data at the time of writing. Monitor the upstream project at the GitHub Repository Global Gateway Filter and the GitHub Repository Container Stock Controller for fixes beyond release 1.0.0.

Workarounds

  • Add a custom filter that extracts auth_warehouse from the session and compares it to the owning warehouse of the targeted container stock record before forwarding the request.
  • Modify ContainerStockController to re-validate warehouse ownership at the controller layer instead of relying solely on the gateway filter.
  • Segregate warehouses into separate Open WES deployments where strict tenant isolation is required.
bash
# Example reverse-proxy rule concept: deny freeze/unfreeze requests
# when the session warehouse header does not match the resource warehouse.
location ~ ^/wes-stock/(freezeContainerStock|unfreezeContainerStock) {
    access_by_lua_block {
        local session_wh = ngx.var.http_x_auth_warehouse
        local target_wh  = resolve_warehouse_for_container(ngx.var.arg_id)
        if session_wh ~= target_wh then
            return ngx.exit(403)
        end
    }
    proxy_pass http://openwes_backend;
}

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.