Vulnerability Database · npm · @oakserver/oak · Version
@oakserver/oak 14.1.0
14.1.0 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 14.1.0.
Critical 0 High 1 Medium 1 Low 0 Unrated 0
-
Released 01 Mar 2024
Status latest release
Licence MIT
Also known from other sources 2
Newer releases 27
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
@oakserver/oak 14.1.0 vulnerabilities
2 vulnerabilities cover @oakserver/oak 14.1.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2024-49770: Path Traversal Vulnerability in @oakserver/oak Allows Access to Hidden Files | 7.5 high | No fix published | 01 Nov 2024 |
| CVE-2025-55152: Oak Server ReDoS Vulnerability in x-forwarded-proto and x-forwarded-for Headers | 5.3 medium | No fix published | 12 Aug 2025 |
Looking for another version, or everything Vulert holds for @oakserver/oak?
Questions
About @oakserver/oak 14.1.0
Is @oakserver/oak 14.1.0 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover @oakserver/oak 14.1.0: 0 critical, 1 high, 1 medium and 0 low. The upgrade Vulert recommends is 14.1.0, and each entry above names the fixed version to move to.
Which version of @oakserver/oak should I use instead of 14.1.0?
14.1.0 is the version Vulert recommends for this release line, which is also the release the publisher currently ships. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 14.1.0 the latest release of @oakserver/oak?
Yes. 14.1.0 is the current release, published 01 Mar 2024. Staying on the current line is what keeps you inside the publisher's fixes.
How do I monitor @oakserver/oak for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @oakserver/oak version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.