VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@oakserver/oak: vulnerability history, versions and safety

@oakserver/oak is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 27 releases, from Nov 2024 to Aug 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 M1
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @oakserver/oak vulnerabilities

Vulert verdict on @oakserver/oak 14.1.0 i

Updated on 22 Oct 2026

Careful: 14.1.0 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 14.1.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 12 Aug 2025 i
  • Highest CVSS 7.5 i
  • With no published fix 2 i
  • Depended on by 1 packages i
  • Stars 5,406 i
  • OpenSSF scorecard 2/10 i
  • Last release 31 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for @oakserver/oak, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
14.1.0 01 Mar 2024 H1 M1 MIT No Details →
14.0.0 25 Feb 2024 H1 M1 MIT No Details →
13.2.5 14 Feb 2024 H1 M1 MIT No Details →
13.2.4 13 Feb 2024 H1 M1 MIT No Details →
13.2.3 13 Feb 2024 H1 M1 MIT No Details →
13.2.2 13 Feb 2024 H1 M1 MIT No Details →
13.2.1 13 Feb 2024 H1 M1 MIT No Details →
13.2.0 13 Feb 2024 H1 M1 MIT No Details →
13.1.0 05 Feb 2024 H1 M1 MIT No Details →
13.0.0 26 Jan 2024 H1 M1 MIT No Details →
12.6.2 12 Jan 2024 H1 M1 MIT No Details →
12.6.1 30 Aug 2023 H1 M1 MIT No Details →
12.6.0 07 Jul 2023 H1 M1 MIT No Details →
12.5.0 21 May 2023 H1 M1 MIT No Details →
12.4.0 01 May 2023 H1 M1 MIT No Details →
12.3.1 30 Apr 2023 H1 M1 MIT No Details →
12.3.0 25 Apr 2023 H1 M1 MIT No Details →
12.2.0 17 Apr 2023 H1 M1 MIT No Details →
12.1.0 06 Mar 2023 H1 M1 MIT No Details →
12.0.1 06 Mar 2023 H1 M1 MIT No Details →
11.0.0 21 Aug 2022 H1 M1 MIT No Details →
10.6.0 23 May 2022 H1 M1 MIT No Details →
10.5.1 24 Mar 2022 H1 M1 MIT No Details →
10.5.0 08 Mar 2022 H1 M1 MIT No Details →
10.4.0 22 Feb 2022 H1 M1 MIT No Details →
10.3.0 21 Feb 2022 H1 M1 MIT No Details →
10.2.1-alpha.1 14 Feb 2022 H1 M1 MIT No Details →

All 27 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @oakserver/oak

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 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

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @oakserver/oak

Is @oakserver/oak safe to use?

Vulert records 2 vulnerabilities for @oakserver/oak in npm: 0 critical, 1 high, 1 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is @oakserver/oak's Vulert package health score?

Vulert scores @oakserver/oak 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of @oakserver/oak affected?

Yes. 14.1.0, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of @oakserver/oak should I use?

14.1.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @oakserver/oak have?

2 vulnerabilities are recorded for @oakserver/oak in the npm ecosystem: 0 critical, 1 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @oakserver/oak vulnerabilities disclosed?

0 vulnerabilities were recorded for @oakserver/oak in the last 12 months, and the oldest entry in this database dates to 01 Nov 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @oakserver/oak are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.