# CVE-2026-26365: Other in Ghost

> Attackers can exploit HTTP request smuggling via custom headers to cause origin servers to misinterpret request bodies, potentially leading to data exposure or modification.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-fhhg-8jv8-7rcw

## What is CVE-2026-26365?

CVE-2026-26365 is a medium-severity vulnerability in Akamai Ghost, published on 23 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2026-26365?


## How do I fix CVE-2026-26365?

No fix has been published for CVE-2026-26365 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-26365 being exploited?

There is no known exploitation of CVE-2026-26365 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26365 and fix it if it is affected.

What it is: CVE-2026-26365 is a medium-severity vulnerability in Akamai Ghost, published on 23 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26365 in the wild and no public exploit code.

Affected product: Akamai Ghost. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26365/ (Markdown: https://insights.sbomify.com/CVE-2026-26365/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26365
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26365
- OSV: https://osv.dev/vulnerability/CVE-2026-26365

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26365/
Summaries are generated and may contain mistakes; the official description above is the record.