# CVE-2025-66373: Other in n/a

> Attackers can smuggle HTTP requests via Akamai Ghost edge servers by exploiting chunked body processing errors, potentially bypassing security controls.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/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:** 4 Dec 2025
- **Updated:** 8 Dec 2025
- **Also known as:** GHSA-xxgg-h2vh-mc43

## What is CVE-2025-66373?

CVE-2025-66373 is a medium-severity vulnerability in n/a, published on 4 Dec 2025. 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 2025-11-17 has a chunked request body processing error that can result in HTTP request smuggling. When Akamai Ghost receives an invalid chunked body that includes a chunk size different from the actual size of the following chunk data, under certain circumstances, Akamai Ghost erroneously forwards the invalid request and subsequent superfluous bytes to the origin server. An attacker could hide a smuggled request in these superfluous bytes. Whether this is exploitable depends on the origin server's behavior and how it processes the invalid request it receives from Akamai Ghost.

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

## Which versions are affected by CVE-2025-66373?

It affects 1 product.


Products: Akamai Akamaighost.

## How do I fix CVE-2025-66373?

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

## Is CVE-2025-66373 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-66373 and fix it if it is affected.

What it is: CVE-2025-66373 is a medium-severity vulnerability in n/a, published on 4 Dec 2025. 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-2025-66373 in the wild and no public exploit code.

Affected product: n/a. 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-2025-66373/ (Markdown: https://insights.sbomify.com/CVE-2025-66373/index.md)
```

## Sources

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

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