HollowByte OpenSSL Memory Exhaustion DoS
First seen Jul 18, 2026 · Updated Jul 18, 2026
HollowByte is a denial-of-service vulnerability in OpenSSL that allows unauthenticated remote attackers to exhaust server memory using a malicious 11-byte payload. The flaw affects any service exposing an OpenSSL-based TLS listener, potentially causing crashes or severe resource exhaustion with minimal attacker effort.
Technical Analysis
HollowByte exploits a parsing or state-handling flaw in OpenSSL's TLS handshake processing, where a crafted 11-byte payload causes the server to allocate disproportionately large memory buffers, leading to memory bloat and eventual denial of service. The attack requires no authentication and can be triggered pre-handshake completion, making it trivially scriptable and low-cost to execute at scale against exposed endpoints. Exploitation likely involves malformed length fields or record headers that bypass input validation checks before buffer allocation occurs. Organizations running AI agent infrastructure that relies on OpenSSL-secured API endpoints, LLM inference servers, or RAG pipeline backends behind TLS termination points are at risk of service disruption, potentially interrupting agent tool-calling workflows, retrieval operations, or model serving availability during an attack.
Affected Systems
Servers using vulnerable versions of OpenSSL for TLS termination, including web servers, reverse proxies, API gateways, and any custom services linking against affected OpenSSL libraries; specific version range not yet disclosed in source reporting
Indicators of Compromise
- No specific IOCs published; indicators would include anomalous spikes in server memory consumption correlating with small (11-byte) incoming TLS payloads
Remediation Steps
- 1
Apply OpenSSL Patch
Monitor OpenSSL project advisories and apply the official patch or update to a fixed OpenSSL version as soon as it is released.
- 2
Deploy Rate Limiting
Implement connection and payload-size rate limiting at load balancers or WAFs to mitigate mass exploitation attempts.
- 3
Monitor Memory Utilization
Set up alerting on abnormal memory growth on TLS-terminating hosts to detect exploitation attempts early.
- 4
Restrict Exposure
Limit direct internet exposure of TLS endpoints where feasible, using upstream DDoS protection services.
- 5
Review Agent Infrastructure Dependencies
Inventory AI agent and RAG pipeline components that terminate TLS via OpenSSL and prioritize patching those endpoints to avoid service interruption.
Industries Most Exposed
Respond to this threat
Pro subscribers get a full AI-generated incident-response playbook for this threat — detection, containment, eradication, and recovery steps — plus an unlimited AI Threat Advisor for questions about your environment.