Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-26365: CWE-444 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in Akamai Ghost

0
Medium
VulnerabilityCVE-2026-26365cvecve-2026-26365cwe-444
Published: Mon Feb 23 2026 (02/23/2026, 00:00:00 UTC)
Source: CVE Database V5
Vendor/Project: Akamai
Product: Ghost

Description

Akamai Ghost on Akamai CDN edge servers before 2026-02-06 mishandles processing of custom hop-by-hop HTTP headers, where an incoming request containing the header "Connection: Transfer-Encoding" could result in a forward request with invalid message framing, depending on the Akamai processing path. This could result in the origin server parsing the request body incorrectly, leading to HTTP request smuggling.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/03/2026, 01:46:46 UTC

Technical Analysis

CVE-2026-26365 is a vulnerability classified under CWE-444 (Inconsistent Interpretation of HTTP Requests) affecting Akamai Ghost, a component deployed on Akamai CDN edge servers. The flaw arises from improper processing of custom hop-by-hop HTTP headers, particularly when an incoming HTTP request includes the header "Connection: Transfer-Encoding." This header is critical because it controls how HTTP message bodies are framed and interpreted. Due to inconsistent handling paths within Akamai Ghost, the forwarded request to the origin server may have invalid or ambiguous message framing. This discrepancy can cause the origin server to misinterpret the request body, enabling HTTP request smuggling attacks. Such attacks exploit differences in how front-end and back-end servers parse HTTP requests, allowing an attacker to smuggle a malicious request that bypasses security filters, poison caches, or hijack user sessions. The vulnerability affects all versions of Akamai Ghost prior to the fix date of February 6, 2026. The CVSS v3.1 base score is 4.0, reflecting a medium severity with network attack vector, high attack complexity, no privileges required, no user interaction, and a scope change. Although no known exploits have been reported, the potential for subtle and impactful exploitation exists, especially in environments relying heavily on Akamai CDN for web traffic delivery.

Potential Impact

The primary impact of this vulnerability is the potential for HTTP request smuggling attacks, which can lead to several security issues. Attackers may bypass security controls such as web application firewalls, poison shared caches causing users to receive malicious content, or hijack user sessions by injecting unauthorized requests. This can compromise the integrity of web applications and potentially lead to data leakage or unauthorized actions. Since Akamai CDN is widely used by enterprises globally to accelerate and secure web traffic, this vulnerability could affect a broad range of organizations, including e-commerce platforms, financial institutions, and government services. The medium CVSS score reflects that while exploitation is complex, the consequences of a successful attack can be significant, especially in high-value target environments. The vulnerability does not impact confidentiality directly but affects integrity and could indirectly affect availability if cache poisoning or request manipulation leads to service disruption.

Mitigation Recommendations

Organizations using Akamai Ghost on Akamai CDN edge servers should prioritize updating to the fixed version released after February 6, 2026, once available. Until patches are applied, administrators should implement strict validation and normalization of HTTP headers at the origin server to detect and reject suspicious or malformed requests containing conflicting hop-by-hop headers, especially "Connection" and "Transfer-Encoding." Deploying Web Application Firewalls (WAFs) with updated signatures that detect HTTP request smuggling patterns can provide an additional layer of defense. Monitoring logs for anomalies in HTTP request framing and unusual header combinations can help identify attempted exploitation. Network segmentation and limiting exposure of critical origin servers can reduce risk. Finally, coordinate with Akamai support for guidance on interim mitigations and ensure CDN configurations do not inadvertently exacerbate the vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2026-02-13T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699c1094be58cf853b5f1af7

Added to database: 2/23/2026, 8:32:20 AM

Last enriched: 3/3/2026, 1:46:46 AM

Last updated: 4/9/2026, 7:12:35 AM

Views: 114

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses