Saleor Afetado por Negação de Serviço via Agrupamento Descontrolado de Consultas GraphQL

The core of this vulnerability lies in Saleor's GraphQL query batching implementation. While intended to improve performance by allowing multiple queries in a single request, the system lacked proper limits on the number of operations. An attacker can craft a malicious HTTP request containing a large array of GraphQL operations, effectively bypassing the per-query complexity limits. This can lead to excessive CPU usage, memory exhaustion, and ultimately, a denial of service, rendering the e-commerce platform unavailable to legitimate users. The lack of authentication means any external user can trigger this vulnerability, significantly expanding the potential attack surface. The impact is particularly severe for businesses relying on Saleor for online sales and customer interactions, as a successful attack could result in lost revenue and reputational damage.

E-commerce businesses utilizing Saleor, particularly those running vulnerable versions (2.0.0–>= 3.23.0-a.0, < 3.23.0a3) in production environments. Shared hosting environments where Saleor instances share resources are at heightened risk, as an attack on one instance could impact others.

• nodejs / server:

# Monitor Saleor server resource usage (CPU, memory)
# Use tools like top, htop, or Prometheus

• generic web:

# Check access logs for unusually large GraphQL requests
# grep -i 'graphql' /var/log/nginx/access.log | grep -i 'batching'

1. 2026-04-08Disclosure

   disclosure

1. Reservado2026-03-23
2. Publicada2026-04-08
3. EPSS atualizado2026-04-16

The primary mitigation for CVE-2026-33756 is to upgrade to a patched version of Saleor. Versions 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118 contain the necessary fixes to limit the number of operations in GraphQL batch requests. If an immediate upgrade is not feasible, consider implementing a Web Application Firewall (WAF) or reverse proxy with rules to limit the size and complexity of incoming GraphQL requests. Specifically, look for rules that restrict the number of operations within a single request. Additionally, monitor Saleor server resources (CPU, memory) for unusual spikes, which could indicate an ongoing attack. After upgrading, confirm the fix by sending a large batch of GraphQL queries and verifying that the server handles them without resource exhaustion.