# CVE-2025-55152: oak: ReDoS in x-forwarded-proto and x-forwarded-for headers

> Attackers can cause denial of service in oak servers by sending specially crafted x-forwarded-proto or x-forwarded-for headers.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2025
- **Updated:** 11 Aug 2025
- **Also known as:** GHSA-r3v7-pc4g-7xp9

## What is CVE-2025-55152?

CVE-2025-55152 is a medium-severity denial of service vulnerability in oakserver oak, published on 9 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

oak is a middleware framework for Deno's native HTTP server, Deno Deploy, Node.js 16.5 and later, Cloudflare Workers and Bun. In versions 17.1.5 and below, it's possible to significantly slow down an oak server with specially crafted values of the x-forwarded-proto or x-forwarded-for headers.

Weakness: CWE-400 (Uncontrolled Resource Consumption), CWE-1333 (Inefficient Regular Expression Complexity)

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

2 open source packages ship an affected version, including @oakserver/oak.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@oakserver/oak` | npm | All versions to 14.1.0 | None |
| `@oakserver/oak` | npm | All versions to 14.1.0 | None |

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

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

## Is CVE-2025-55152 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55152 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55152 is a medium-severity denial of service vulnerability in oakserver oak, published on 9 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55152 exists.

Affected packages and fixed versions:
- @oakserver/oak (npm): affected all versions up to 14.1.0; no fix listed
- @oakserver/oak (npm): affected all versions up to 14.1.0; no fix listed

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-55152/ (Markdown: https://insights.sbomify.com/CVE-2025-55152/index.md)
```

## Sources

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

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