Oak Server has ReDoS in x-forwarded-proto and x-forwarded-for headers

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS

• CVE-2025-55152: 0.41% estimated exploitation activity in the next 30 days; percentile 35.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary With specially crafted value of the x-forwarded-proto or x-forwarded-for headers, it's possible to significantly slow down an oak server. Vulnerable Code - https://github.com/oakserver/oak/blob/v17.1.5/request.ts#L87 - https://github.com/oakserver/oak/blob/v17.1.5/request.ts#L142 PoC - setup - server.ts - client.ts - run Impact A specially crafted value of the x-forwarded-proto or x-forwarded-for headers can be used to significantly slow down an oak server. Similar Issues - https://github.com/denoland/deno/security/advisories/GHSA-jc97-h3h9-7xh6 - https://github.com/denoland/deno/pull/17722 - https://github.com/websockets/ws/security/advisories/GHSA-6fc8-4gx4-v693 - https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff

Published by the source

12 Aug 2025, 00:15 UTC

Last modified by the source

12 Aug 2025, 00:15 UTC

Source last checked

26 Oct 2026, 12:37 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-r3v7-pc4g-7xp9

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-r3v7-pc4g-7xp9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-55152

Advisory: Oak Server has ReDoS in x-forwarded-proto and x-forwarded-for headers
IDs: CVE-2025-55152, GHSA-r3v7-pc4g-7xp9
Record: https://patchnext.com/advisories/cve-2025-55152 (revision 2, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @oakserver/oak: affected <= 14.1.0

## Suggested inspection (read-only)
- `npm ls @oakserver/oak --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @oakserver/oak.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-r3v7-pc4g-7xp9 (OSV record GHSA-r3v7-pc4g-7xp9 lists affected ranges: npm @oakserver/oak >=0 <=14.1.0)
- Verified: https://github.com/advisories/GHSA-r3v7-pc4g-7xp9 (GitHub-reviewed advisory GHSA-r3v7-pc4g-7xp9 lists affected ranges: npm @oakserver/oak >=0 <=14.1.0)

Commands are suggestions: review each one before running it.