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

CVE-2026-94250: Apache APISIX Batch-Requests DoS Vulnerability

CVE-2026-94250 is a denial of service vulnerability in Apache APISIX batch-requests plugin that allows unauthenticated attackers to cause memory exhaustion. This article covers technical details, affected versions, impact, and mitigation.

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

CVE-2026-94250 is a resource exhaustion vulnerability in the batch-requests plugin of Apache APISIX. An unauthenticated remote attacker can drive a gateway worker process into an out-of-memory (OOM) condition when a route uses the batch-requests plugin and exposes the batch endpoint publicly. The flaw is tracked as [CWE-770: Allocation of Resources Without Limits or Throttling] and affects Apache APISIX versions 1.3.0 through 3.18.0. Apache has released version 3.19.0 to address the issue.

Critical Impact

Unauthenticated attackers can crash APISIX gateway workers via memory exhaustion, disrupting traffic for all services fronted by the gateway.

Affected Products

  • Apache APISIX 1.3.0 through 3.18.0
  • Deployments exposing the batch-requests plugin on a public route
  • Any downstream services routed through an impacted APISIX instance

Discovery Timeline

  • 2026-10-01 - CVE-2026-94250 published to NVD
  • 2026-10-01 - Last updated in NVD database

Technical Details for CVE-2026-94250

Vulnerability Analysis

Apache APISIX is a dynamic, high-performance API gateway built on OpenResty and Nginx. The batch-requests plugin allows clients to pack multiple HTTP requests into a single call, which the gateway then unpacks and dispatches internally. The plugin accepts a JSON payload describing the sub-requests to execute.

The vulnerability stems from the absence of enforced limits on the size or count of batched sub-requests. An unauthenticated caller can submit a crafted payload large enough to consume all available memory in a worker process. When the worker exceeds its memory budget, the operating system terminates it, interrupting in-flight traffic.

Because APISIX fronts upstream services, a single attacker can degrade availability for every API and application behind the gateway. The attack requires no credentials and no user interaction.

Root Cause

The batch-requests plugin fails to apply input size caps, per-request counts, or throttling to the batch endpoint. Without these controls, the plugin allocates memory proportional to attacker-controlled input, resulting in unbounded growth within the worker process.

Attack Vector

The attack is delivered over the network against any route configured with the batch-requests plugin where the batch endpoint is publicly reachable. The attacker issues HTTP POST requests containing a very large or deeply nested batch payload. Repeated requests magnify memory pressure until the worker is terminated.

No verified exploit code is published for this issue. See the Apache Mailing List Thread and the Openwall OSS-Security Message for the vendor advisory details.

Detection Methods for CVE-2026-94250

Indicators of Compromise

  • Repeated HTTP POST requests to routes bound to the batch-requests plugin with abnormally large Content-Length values.
  • APISIX worker processes being killed by the Linux OOM killer, visible in dmesg or /var/log/messages.
  • Spikes in nginx worker memory usage followed by worker process exited on signal 9 entries in error.log.

Detection Strategies

  • Audit APISIX route configurations to enumerate every route that enables the batch-requests plugin and determine whether it is publicly exposed.
  • Alert on anomalous request body sizes to batch endpoints relative to a baseline of normal traffic.
  • Correlate gateway worker restarts with upstream request patterns to identify DoS attempts.

Monitoring Recommendations

  • Collect APISIX error.log and system dmesg output into a central log pipeline for OOM event correlation.
  • Track per-worker resident set size (RSS) metrics and set alerts for rapid growth.
  • Monitor APISIX Prometheus metrics for sudden drops in apisix_http_status throughput that align with memory spikes.

How to Mitigate CVE-2026-94250

Immediate Actions Required

  • Upgrade Apache APISIX to version 3.19.0 or later, which contains the vendor fix.
  • Inventory all routes using the batch-requests plugin and restrict exposure until patching completes.
  • Place rate limiting and request body size limits in front of batch endpoints at the perimeter.

Patch Information

Apache has resolved the issue in Apache APISIX 3.19.0. Operators running any release between 1.3.0 and 3.18.0 inclusive should upgrade. Refer to the Apache Mailing List Thread for official vendor guidance.

Workarounds

  • Disable the batch-requests plugin on routes that do not require it.
  • Bind the batch endpoint to an internal network interface or restrict access via IP allowlists.
  • Apply the APISIX limit-req or limit-count plugin and configure request body size limits in Nginx (client_max_body_size) to cap attacker-controlled input.
bash
# Configuration example
# Disable batch-requests plugin globally in conf/config.yaml
plugins:
  # - batch-requests   # commented out to disable
  - limit-req
  - limit-count

nginx_config:
  http:
    client_max_body_size: 1m

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.