CVE-2026-84857: Sigoden AIChat RCE Vulnerability

CVE-2026-84857 Overview

CVE-2026-84857 is an uncontrolled resource consumption vulnerability [CWE-400] in sigoden aichat versions up to 0.30.4. The flaw resides in an unspecified function within src/serve.rs, which handles the application's API endpoint. Attackers can send crafted HTTP requests that trigger uncontrolled memory allocation on the server. The exploit has been published, and the vendor did not respond to the disclosure. Remote attackers can trigger the condition without authentication or user interaction.

Critical Impact
Remote, unauthenticated attackers can exhaust server memory by sending oversized or malformed request bodies to the aichat API endpoint, causing a denial-of-service condition.

Affected Products

sigoden aichat versions up to and including 0.30.4
The src/serve.rs API endpoint component
Deployments exposing the aichat HTTP server

Discovery Timeline

2026-09-02 - CVE-2026-84857 published to NVD
2026-09-02 - Last updated in NVD database

Technical Details for CVE-2026-84857

Vulnerability Analysis

The vulnerability sits in the request-handling path of src/serve.rs, which exposes the aichat API over HTTP. The server accepts request bodies without enforcing an upper bound on the amount of memory allocated during parsing. An attacker can submit a request that causes the process to allocate memory proportional to attacker-controlled input.

Repeated or concurrent malicious requests inflate the resident memory of the aichat process. On resource-constrained hosts, this leads to out-of-memory conditions and process termination. The public GitHub disclosure documents the request-body denial-of-service pattern.

Root Cause

The root cause is uncontrolled resource consumption during API request processing. The serve.rs handler reads and buffers incoming request bodies without validating a maximum size or applying streaming limits before allocation. This behavior maps directly to CWE-400.

Attack Vector

The attack vector is network-based and requires no authentication or user interaction. An attacker sends a single crafted HTTP request, or a small burst of them, to the exposed aichat API endpoint. Memory allocation grows until the operating system reclaims the process or the host becomes unresponsive.

A public proof-of-concept is available in the GitHub CVE-2026-84857 DoS Report. See the VulDB entry for CVE-2026-84857 for additional context.

Detection Methods for CVE-2026-84857

Indicators of Compromise

HTTP requests to aichat API endpoints with abnormally large Content-Length headers or chunked bodies from a single source.
Sudden growth in resident set size (RSS) of the aichat process followed by process termination or restart.
Repeated OOM-killer events in dmesg or systemd journal correlated with aichat activity.

Detection Strategies

Monitor reverse-proxy or web application firewall logs for outbound requests to / and other aichat routes with oversized payloads.
Baseline normal request sizes to the aichat service and alert on statistical outliers.
Correlate host memory saturation events with concurrent inbound HTTP traffic to the aichat listener.

Monitoring Recommendations

Track process-level memory metrics for aichat with a threshold alert well below host capacity.
Enable rate-limiting counters and log per-source request volume at the ingress tier.
Ingest host and proxy telemetry into a centralized analytics platform to enable cross-source correlation of memory pressure and traffic spikes.

How to Mitigate CVE-2026-84857

Immediate Actions Required

Restrict network exposure of the aichat API endpoint to trusted networks or authenticated reverse proxies.
Place a reverse proxy in front of aichat to enforce a strict maximum request body size.
Apply rate limiting per source IP to reduce the impact of repeated abusive requests.

Patch Information

At the time of publication, the enriched CVE data indicates the vendor was contacted but did not respond, and no fixed version is listed. Monitor the sigoden aichat repository for updates beyond version 0.30.4, and review the VulDB vulnerability record #398132 for changes to remediation status.

Workarounds

Configure an upstream proxy such as nginx or Caddy to enforce client_max_body_size limits before traffic reaches aichat.
Deploy aichat within a container or systemd unit that enforces memory limits, so the service is restarted rather than starving the host.
Require authentication at the proxy layer to prevent unauthenticated internet-facing exposure of the API endpoint.

bash

# Example nginx snippet to bound request bodies in front of aichat
server {
    listen 443 ssl;
    server_name aichat.example.com;

    client_max_body_size 1m;
    client_body_buffer_size 16k;

    limit_req_zone $binary_remote_addr zone=aichat:10m rate=10r/s;

    location / {
        limit_req zone=aichat burst=20 nodelay;
        proxy_pass http://127.0.0.1:8000;
    }
}