VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

Microsoft.OpenApi: vulnerability history, versions and safety

Microsoft.OpenApi is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 49 releases, first recorded in Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 30 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all Microsoft.OpenApi vulnerabilities

Vulert verdict on Microsoft.OpenApi 3.11.0 i

Updated on 23 Oct 2026

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

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 3.11.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 30 Jun 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 1,611 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by NuGet, 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 Microsoft.OpenApi, 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
3.11.0 19 Oct 2026 none MIT — Details →
2.13.0 19 Oct 2026 none MIT — Details →
2.12.2 20 Aug 2026 none MIT — Details →
1.6.31 20 Aug 2026 none MIT — Details →
3.10.2 20 Aug 2026 none MIT — Details →
2.12.1 20 Aug 2026 none MIT — Details →
1.6.30 13 Aug 2026 none MIT — Details →
2.12.0 12 Aug 2026 none MIT — Details →
3.10.0 12 Aug 2026 none MIT — Details →
2.11.0 15 Jul 2026 none MIT — Details →
3.9.0 15 Jul 2026 none MIT — Details →
2.10.0 06 Jul 2026 none MIT — Details →
3.8.0 06 Jul 2026 none MIT — Details →
2.9.0 10 Jun 2026 none MIT — Details →
3.7.0 10 Jun 2026 none MIT — Details →
2.8.0 01 Jun 2026 none MIT — Details →
3.6.0 01 Jun 2026 none MIT — Details →
3.5.5 29 May 2026 none MIT — Details →
2.7.6 29 May 2026 none MIT — Details →
2.7.5 26 May 2026 none MIT — Details →
3.5.4 26 May 2026 none MIT — Details →
2.7.4 27 Apr 2026 H1 MIT Yes Details →
3.5.3 27 Apr 2026 none MIT — Details →
1.6.29 14 Apr 2026 none MIT — Details →
2.7.3 14 Apr 2026 H1 MIT Yes Details →
3.5.2 14 Apr 2026 none MIT — Details →
2.7.2 01 Apr 2026 H1 MIT Yes Details →
3.5.1 31 Mar 2026 none MIT — Details →
3.5.0 20 Mar 2026 none MIT — Details →
2.7.1 20 Mar 2026 H1 MIT Yes Details →
2.7.0 05 Mar 2026 H1 MIT Yes Details →
3.4.0 05 Mar 2026 none MIT — Details →
2.6.1 22 Jan 2026 H1 MIT Yes Details →
3.3.1 22 Jan 2026 none MIT — Details →
2.6.0 21 Jan 2026 H1 MIT Yes Details →
3.3.0 21 Jan 2026 none MIT — Details →
2.5.0 19 Jan 2026 H1 MIT Yes Details →
3.2.0 19 Jan 2026 none MIT — Details →
3.1.3 16 Jan 2026 none MIT — Details →
2.4.3 16 Jan 2026 H1 MIT Yes Details →
2.4.2 06 Jan 2026 H1 MIT Yes Details →
3.1.2 06 Jan 2026 none MIT — Details →
3.1.1 18 Dec 2025 none MIT — Details →
2.4.1 18 Dec 2025 H1 MIT Yes Details →
2.4.0 17 Dec 2025 H1 MIT Yes Details →
3.0.3 16 Dec 2025 none MIT — Details →
2.3.12 16 Dec 2025 H1 MIT Yes Details →
2.3.11 08 Dec 2025 H1 MIT Yes Details →
3.0.2 08 Dec 2025 none MIT — Details →
2.3.10 17 Nov 2025 H1 MIT Yes Details →
3.0.1 17 Nov 2025 none MIT — Details →
3.0.0 11 Nov 2025 none MIT — Details →
2.3.9 06 Nov 2025 H1 MIT Yes Details →
2.3.8 27 Oct 2025 H1 MIT Yes Details →
2.3.7 24 Oct 2025 H1 MIT Yes Details →
2.3.6 20 Oct 2025 H1 MIT Yes Details →
2.3.5 14 Oct 2025 H1 MIT Yes Details →
1.6.28 06 Oct 2025 none MIT — Details →
2.3.4 06 Oct 2025 H1 MIT Yes Details →
2.3.3 02 Oct 2025 H1 MIT Yes Details →
1.6.27 02 Oct 2025 none MIT — Details →
1.6.26 22 Sep 2025 none MIT — Details →
2.3.2 19 Sep 2025 H1 MIT Yes Details →
2.3.1 08 Sep 2025 H1 MIT Yes Details →
2.3.0 29 Aug 2025 H1 MIT Yes Details →
2.2.0 25 Aug 2025 H1 MIT Yes Details →
1.6.25 22 Aug 2025 none MIT — Details →
2.1.0 20 Aug 2025 H1 MIT Yes Details →
2.0.1 18 Aug 2025 H1 MIT Yes Details →
2.0.0 10 Jul 2025 H1 MIT Yes Details →
2.0.0-preview.31 03 Jul 2025 H1 MIT Yes Details →
2.0.0-preview.30 02 Jul 2025 H1 MIT Yes Details →
2.0.0-preview.29 18 Jun 2025 H1 MIT Yes Details →
2.0.0-preview.28 16 Jun 2025 H1 MIT Yes Details →
2.0.0-preview.27 13 Jun 2025 H1 MIT Yes Details →
2.0.0-preview.26 12 Jun 2025 H1 MIT Yes Details →
2.0.0-preview.25 10 Jun 2025 H1 MIT Yes Details →
2.0.0-preview.23 03 Jun 2025 H1 MIT Yes Details →
2.0.0-preview.22 02 Jun 2025 H1 MIT Yes Details →
2.0.0-preview.21 21 May 2025 H1 MIT Yes Details →
2.0.0-preview.20 20 May 2025 H1 MIT Yes Details →
2.0.0-preview.19 16 May 2025 H1 MIT Yes Details →
2.0.0-preview.18 13 May 2025 H1 MIT Yes Details →
2.0.0-preview.17 16 Apr 2025 H1 MIT Yes Details →
1.6.24 01 Apr 2025 none MIT — Details →
2.0.0-preview.16 20 Mar 2025 H1 MIT Yes Details →
2.0.0-preview.15 19 Mar 2025 H1 MIT Yes Details →
2.0.0-preview.14 18 Mar 2025 H1 MIT Yes Details →
2.0.0-preview.13 14 Mar 2025 H1 MIT Yes Details →
2.0.0-preview.12 07 Mar 2025 H1 MIT Yes Details →
2.0.0-preview.11 03 Mar 2025 H1 MIT Yes Details →
1.6.23 20 Dec 2024 none MIT — Details →
1.6.22 30 Sep 2024 none MIT — Details →
1.6.21 05 Sep 2024 none MIT — Details →
1.6.18 23 Aug 2024 none MIT — Details →
1.6.17 06 Aug 2024 none MIT — Details →
1.6.16 30 Jul 2024 none MIT — Details →
1.6.15 18 Jun 2024 none MIT — Details →
1.6.14 06 Mar 2024 none MIT — Details →
1.6.13 29 Jan 2024 none MIT — Details →
1.6.12 16 Jan 2024 none — — Details →
1.6.11 22 Nov 2023 none — — Details →
1.6.10 30 Oct 2023 none — — Details →
1.6.9 26 Sep 2023 none — — Details →
1.6.8 07 Sep 2023 none — — Details →
1.6.7 01 Sep 2023 none — — Details →
1.6.6 24 Jul 2023 none — — Details →
1.6.5 19 Jun 2023 none — — Details →
1.6.4 04 May 2023 none — — Details →
1.6.4-preview4 17 Apr 2023 none — — Details →
1.6.4-preview3 12 Apr 2023 none — — Details →
1.6.4-preview2 11 Apr 2023 none — — Details →
1.6.4-preview1 30 Mar 2023 none — — Details →
1.6.3 07 Mar 2023 none — — Details →
1.6.2 21 Feb 2023 none — — Details →
1.6.1 13 Feb 2023 none — — Details →
1.6.0 31 Jan 2023 none — — Details →
1.5.0 17 Jan 2023 none — — Details →
1.4.5 06 Dec 2022 none — — Details →
1.4.4 21 Nov 2022 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for Microsoft.OpenApi

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-49451: Microsoft.OpenAPI Circular Schema Reference Vulnerability Leading to Process Termination 7.5 high 2.7.5 30 Jun 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: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 Microsoft.OpenApi

Is Microsoft.OpenApi safe to use?

Vulert records 1 vulnerabilities for Microsoft.OpenApi in NuGet: 0 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 Microsoft.OpenApi's Vulert package health score?

Vulert scores Microsoft.OpenApi 81/100, which reads as in good shape. 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 Microsoft.OpenApi affected?

No. 3.11.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 Microsoft.OpenApi have?

1 vulnerability is recorded for Microsoft.OpenApi in the NuGet ecosystem: 0 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 Microsoft.OpenApi vulnerabilities disclosed?

1 vulnerability was recorded for Microsoft.OpenApi in the last 12 months, and the oldest entry in this database dates to 30 Jun 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 Microsoft.OpenApi 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 Microsoft.OpenApi for upcoming vulnerabilities?

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