VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

orval: vulnerability history, versions and safety

orval is a package in the npm ecosystem. Vulert records 12 vulnerabilities for it across 96 releases, first recorded in Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
12 vulnerabilities recorded C11 H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
12 in the last 12 months

Most recent disclosure 03 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all orval vulnerabilities

Vulert verdict on orval 8.44.0 i

Updated on 22 Oct 2026

Good news: 8.44.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 12.

Package health score 63/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

What to do: Stay on 8.44.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 8.44.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 8.44.0 — unaffected i
  • Vulnerabilities on record 12 over 1 year · 12 in the last year i
  • Latest disclosure 03 Sep 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 0 i
  • Depended on by 14 packages i
  • Stars 6,547 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 orval, 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
8.44.0 21 Oct 2026 none MIT — Details →
8.43.0 14 Oct 2026 none MIT — Details →
8.42.0 13 Oct 2026 none MIT — Details →
8.41.0 08 Oct 2026 none MIT — Details →
8.40.0 04 Oct 2026 none MIT — Details →
8.39.0 30 Sep 2026 none MIT — Details →
8.38.0 26 Sep 2026 none MIT — Details →
8.37.0 23 Sep 2026 none MIT — Details →
8.36.0 21 Sep 2026 none MIT — Details →
8.35.0 20 Sep 2026 none MIT — Details →
8.34.0 18 Sep 2026 none MIT — Details →
8.33.0 13 Sep 2026 none MIT — Details →
8.32.0 12 Sep 2026 none MIT — Details →
8.31.0 10 Sep 2026 none MIT — Details →
8.30.0 07 Sep 2026 none MIT — Details →
8.29.0 06 Sep 2026 none MIT — Details →
8.28.1 03 Sep 2026 none MIT — Details →
8.28.0 03 Sep 2026 none MIT — Details →
8.27.0 29 Aug 2026 none MIT — Details →
8.26.0 23 Aug 2026 none MIT — Details →
8.25.0 21 Aug 2026 none MIT — Details →
8.24.0 08 Aug 2026 none MIT — Details →
8.23.0 25 Jul 2026 none MIT — Details →
8.22.0 14 Jul 2026 none MIT — Details →
8.21.0 12 Jul 2026 H1 MIT Yes Details →
8.20.0 03 Jul 2026 C11 H1 MIT Yes Details →
8.19.0 24 Jun 2026 C11 H1 MIT Yes Details →
8.18.0 18 Jun 2026 C11 H1 MIT Yes Details →
8.17.0 11 Jun 2026 C11 H1 MIT Yes Details →
8.16.0 08 Jun 2026 C11 H1 MIT Yes Details →
8.15.0 02 Jun 2026 C11 H1 MIT Yes Details →
8.14.0 29 May 2026 C11 H1 MIT Yes Details →
8.13.0 26 May 2026 C11 H1 MIT Yes Details →
8.12.3 22 May 2026 C11 H1 MIT Yes Details →
8.12.2 21 May 2026 C11 H1 MIT Yes Details →
8.12.1 21 May 2026 C11 H1 MIT Yes Details →
8.11.0 18 May 2026 C11 H1 MIT Yes Details →
8.10.0 12 May 2026 C11 H1 MIT Yes Details →
8.9.1 03 May 2026 C11 H1 MIT Yes Details →
8.9.0 26 Apr 2026 C11 H1 MIT Yes Details →
8.8.1 20 Apr 2026 C11 H1 MIT Yes Details →
8.8.0 15 Apr 2026 C11 H1 MIT Yes Details →
8.7.0 09 Apr 2026 C11 H1 MIT Yes Details →
8.6.2 23 Mar 2026 C11 H1 MIT Yes Details →
8.6.1 23 Mar 2026 C11 H1 MIT Yes Details →
8.6.0 23 Mar 2026 C11 H1 MIT Yes Details →
8.5.3 06 Mar 2026 C11 H1 MIT Yes Details →
8.5.2 04 Mar 2026 C11 H1 MIT Yes Details →
8.5.1 27 Feb 2026 C11 H1 MIT Yes Details →
8.5.0 25 Feb 2026 C11 H1 MIT Yes Details →
8.4.2 21 Feb 2026 C11 H1 MIT Yes Details →
8.4.1 19 Feb 2026 C11 H1 MIT Yes Details →
8.4.0 16 Feb 2026 C11 H1 MIT Yes Details →
8.3.0 11 Feb 2026 C11 H1 MIT Yes Details →
8.2.0 30 Jan 2026 C11 H1 MIT Yes Details →
7.21.0 30 Jan 2026 C11 H1 MIT Yes Details →
8.1.0 26 Jan 2026 C11 H1 MIT Yes Details →
8.0.3 22 Jan 2026 C11 H1 MIT Yes Details →
7.20.0 22 Jan 2026 C11 H1 MIT Yes Details →
7.19.0 21 Jan 2026 C11 H1 MIT Yes Details →
8.0.2 19 Jan 2026 C11 H1 MIT Yes Details →
8.0.1 16 Jan 2026 C11 H1 MIT Yes Details →
8.0.0 14 Jan 2026 C11 H1 MIT Yes Details →
8.0.0-rc.6 12 Jan 2026 C11 H1 MIT Yes Details →
7.18.0 10 Jan 2026 C11 H1 MIT Yes Details →
8.0.0-rc.5 23 Dec 2025 C11 H1 MIT Yes Details →
8.0.0-rc.4 21 Dec 2025 C11 H1 MIT Yes Details →
7.17.2 21 Dec 2025 C11 H1 MIT Yes Details →
8.0.0-rc.3 06 Dec 2025 C11 H1 MIT Yes Details →
7.17.0 24 Nov 2025 C11 H1 MIT Yes Details →
7.16.1 21 Nov 2025 C11 H1 MIT Yes Details →
8.0.0-rc.2 14 Nov 2025 C11 H1 MIT Yes Details →
7.16.0 31 Oct 2025 C11 H1 MIT Yes Details →
8.0.0-rc.1 30 Oct 2025 C11 H1 MIT Yes Details →
8.0.0-rc.0 27 Oct 2025 C11 H1 MIT Yes Details →
7.15.0 25 Oct 2025 C11 H1 MIT Yes Details →
7.14.0 19 Oct 2025 C11 H1 MIT Yes Details →
7.13.2 07 Oct 2025 C11 H1 MIT Yes Details →
7.13.1 05 Oct 2025 C11 H1 MIT Yes Details →
7.13.0 28 Sep 2025 C11 H1 MIT Yes Details →
7.12.2 26 Sep 2025 C11 H1 MIT Yes Details →
7.12.1 24 Sep 2025 C11 H1 MIT Yes Details →
7.11.2 02 Aug 2025 C11 H1 MIT Yes Details →
7.11.1 31 Jul 2025 C11 H1 MIT Yes Details →
7.11.0 31 Jul 2025 C11 H1 MIT Yes Details →
7.10.0 12 Jun 2025 C11 H1 MIT Yes Details →
7.9.0 27 Apr 2025 C11 H1 MIT Yes Details →
7.8.0 03 Apr 2025 C11 H1 MIT Yes Details →
7.7.0 13 Mar 2025 C11 H1 MIT Yes Details →
7.6.0 27 Feb 2025 C11 H1 MIT Yes Details →
7.5.0 03 Feb 2025 C11 H1 MIT Yes Details →
7.4.1 09 Jan 2025 C11 H1 MIT Yes Details →
7.4.0 07 Jan 2025 C11 H1 MIT Yes Details →
7.3.0 16 Nov 2024 C11 H1 MIT Yes Details →
7.2.0 22 Oct 2024 C11 H1 MIT Yes Details →
7.1.1 17 Sep 2024 C11 H1 MIT Yes Details →
7.1.0 02 Sep 2024 C11 H1 MIT Yes Details →
7.0.1 05 Aug 2024 C11 H1 MIT Yes Details →
7.0.0 22 Jul 2024 C11 H1 MIT Yes Details →
6.31.0 25 Jun 2024 C11 H1 MIT Yes Details →
6.30.2 07 Jun 2024 C11 H1 — Yes Details →
6.30.1 07 Jun 2024 C11 H1 — Yes Details →
6.30.0 07 Jun 2024 C11 H1 — Yes Details →
6.29.1 17 May 2024 C11 H1 — Yes Details →
6.29.0 17 May 2024 C11 H1 — Yes Details →
6.28.2 25 Apr 2024 C11 H1 — Yes Details →
6.28.1 25 Apr 2024 C11 H1 — Yes Details →
6.28.0 25 Apr 2024 C11 H1 — Yes Details →
6.27.1 11 Apr 2024 C11 H1 — Yes Details →
6.27.0 11 Apr 2024 C11 H1 — Yes Details →
6.26.0 01 Apr 2024 C11 H1 — Yes Details →
6.25.0 17 Feb 2024 C11 H1 — Yes Details →
6.24.0 31 Jan 2024 C11 H1 — Yes Details →
6.23.0 19 Dec 2023 C11 H1 — Yes Details →
6.22.1 06 Dec 2023 C11 H1 — Yes Details →
6.22.0 06 Dec 2023 C11 H1 — Yes Details →
6.21.0 28 Nov 2023 C11 H1 — Yes Details →
6.20.0 09 Nov 2023 C11 H1 — Yes Details →
6.19.1 24 Oct 2023 C11 H1 — Yes Details →
6.19.0 19 Oct 2023 C11 H1 — Yes Details →

The newest 120 of 330 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 12

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

03 Vulnerabilities

Recorded vulnerabilities for orval

The 3 most severe of 12 vulnerabilities recorded for this package

Search all 12 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-71866: Orval Package Suffers from Import-Time RCE via Schema Property Name Injection 9.3 critical 8.21.0 02 Sep 2026
CVE-2026-72716: Orval Critical RCE Vulnerability via Unescaped Query Parameter Default 9.3 critical 8.21.0 02 Sep 2026
CVE-2026-62680: Orval Package Suffers from SSRF and File Inclusion Vulnerabilities 7.1 high 8.22.0 02 Sep 2026

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 →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Add Vulert as a Preferred Source

Questions

About orval

Is orval safe to use?

Vulert records 12 vulnerabilities for orval in npm: 11 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is orval's Vulert package health score?

Vulert scores orval 63/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).

Is the latest version of orval affected?

No. 8.44.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does orval have?

12 vulnerabilities are recorded for orval in the npm ecosystem: 11 critical, 1 high, 0 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 orval vulnerabilities disclosed?

12 vulnerabilities were recorded for orval in the last 12 months, and the oldest entry in this database dates to 02 Sep 2026. 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 orval 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 orval for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the orval version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.