VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

swagger-ui: vulnerability history, versions and safety

swagger-ui is a package in the npm ecosystem. Vulert records 15 vulnerabilities for it across 0 release, from Jun 2019 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
15 vulnerabilities recorded C4 H1 M10
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 swagger-ui vulnerabilities

Vulert verdict on swagger-ui 5.34.0 i

Updated on 22 Oct 2026

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

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

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

  • Current release 5.34.0 — unaffected i
  • Vulnerabilities on record 15 over 2 years · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 33 packages i
  • Stars 29,041 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence Apache-2.0 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 swagger-ui, 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
5.34.0 19 Oct 2026 none Apache-2.0 — Details →
5.33.3 15 Oct 2026 none Apache-2.0 — Details →
5.33.2 12 Oct 2026 none Apache-2.0 — Details →
5.33.1 01 Oct 2026 none Apache-2.0 — Details →
5.33.0 16 Sep 2026 none Apache-2.0 — Details →
5.32.15 04 Sep 2026 none Apache-2.0 — Details →
5.32.14 18 Aug 2026 none Apache-2.0 — Details →
5.32.13 11 Aug 2026 none Apache-2.0 — Details →
5.32.12 03 Aug 2026 none Apache-2.0 — Details →
5.32.11 22 Jul 2026 none Apache-2.0 — Details →
5.32.10 21 Jul 2026 none Apache-2.0 — Details →
5.32.9 17 Jul 2026 none Apache-2.0 — Details →
5.32.8 23 Jun 2026 none Apache-2.0 — Details →
5.32.7 22 Jun 2026 none Apache-2.0 — Details →
5.32.6 12 May 2026 none Apache-2.0 — Details →
5.32.5 27 Apr 2026 none Apache-2.0 — Details →
5.32.4 15 Apr 2026 none Apache-2.0 — Details →
5.32.3 14 Apr 2026 none Apache-2.0 — Details →
5.32.2 07 Apr 2026 none Apache-2.0 — Details →
5.32.1 17 Mar 2026 none Apache-2.0 — Details →
5.32.0 27 Feb 2026 none Apache-2.0 — Details →
5.31.2 20 Feb 2026 none Apache-2.0 — Details →
5.31.1 16 Feb 2026 none Apache-2.0 — Details →
5.31.0 11 Dec 2025 none Apache-2.0 — Details →
5.30.3 25 Nov 2025 none Apache-2.0 — Details →
5.30.2 04 Nov 2025 none Apache-2.0 — Details →
5.30.1 31 Oct 2025 none Apache-2.0 — Details →
5.30.0 27 Oct 2025 none Apache-2.0 — Details →
5.29.5 17 Oct 2025 none Apache-2.0 — Details →
5.29.4 10 Oct 2025 none Apache-2.0 — Details →
5.29.3 03 Oct 2025 none Apache-2.0 — Details →
5.29.2 02 Oct 2025 none Apache-2.0 — Details →
5.29.1 29 Sep 2025 none Apache-2.0 — Details →
5.29.0 09 Sep 2025 none Apache-2.0 — Details →
5.28.1 03 Sep 2025 none Apache-2.0 — Details →
5.28.0 28 Aug 2025 none Apache-2.0 — Details →
5.27.1 01 Aug 2025 none Apache-2.0 — Details →
5.27.0 16 Jul 2025 none Apache-2.0 — Details →
5.26.2 07 Jul 2025 none Apache-2.0 — Details →
5.26.1 07 Jul 2025 none Apache-2.0 — Details →
5.26.0 02 Jul 2025 none Apache-2.0 — Details →
5.25.4 01 Jul 2025 none Apache-2.0 — Details →
5.25.3 26 Jun 2025 none Apache-2.0 — Details →
5.25.2 18 Jun 2025 none Apache-2.0 — Details →
5.25.1 18 Jun 2025 none Apache-2.0 — Details →
5.25.0 18 Jun 2025 none Apache-2.0 — Details →
5.24.2 16 Jun 2025 none Apache-2.0 — Details →
5.24.1 10 Jun 2025 none Apache-2.0 — Details →
5.24.0 05 Jun 2025 none Apache-2.0 — Details →
5.23.0 05 Jun 2025 none Apache-2.0 — Details →
5.22.0 21 May 2025 none Apache-2.0 — Details →
5.21.0 13 Apr 2025 none Apache-2.0 — Details →
5.20.8 10 Apr 2025 none Apache-2.0 — Details →
5.20.7 07 Apr 2025 none Apache-2.0 — Details →
5.20.6 04 Apr 2025 none Apache-2.0 — Details →
5.20.5 03 Apr 2025 none Apache-2.0 — Details →
5.20.4 03 Apr 2025 none Apache-2.0 — Details →
5.20.3 02 Apr 2025 none Apache-2.0 — Details →
5.20.2 27 Mar 2025 none Apache-2.0 — Details →
5.20.1 10 Mar 2025 none Apache-2.0 — Details →
5.20.0 27 Feb 2025 none Apache-2.0 — Details →
5.19.0 17 Feb 2025 none Apache-2.0 — Details →
5.18.3 28 Jan 2025 none Apache-2.0 — Details →
5.18.2 07 Nov 2024 none Apache-2.0 — Details →
5.18.1 05 Nov 2024 none Apache-2.0 — Details →
5.18.0 05 Nov 2024 none Apache-2.0 — Details →
5.17.14 28 May 2024 none Apache-2.0 — Details →
5.17.13 27 May 2024 none Apache-2.0 — Details →
5.17.12 21 May 2024 none Apache-2.0 — Details →
5.17.11 21 May 2024 none Apache-2.0 — Details →
5.17.10 15 May 2024 none Apache-2.0 — Details →
5.17.9 13 May 2024 none Apache-2.0 — Details →
5.17.8 13 May 2024 none Apache-2.0 — Details →
5.17.7 09 May 2024 none Apache-2.0 — Details →
5.17.6 07 May 2024 none Apache-2.0 — Details →
5.17.5 06 May 2024 none Apache-2.0 — Details →
5.17.4 06 May 2024 none Apache-2.0 — Details →
5.17.3 30 Apr 2024 none Apache-2.0 — Details →
5.17.2 25 Apr 2024 none Apache-2.0 — Details →
5.17.1 24 Apr 2024 none Apache-2.0 — Details →
5.17.0 22 Apr 2024 none Apache-2.0 — Details →
5.16.2 19 Apr 2024 none Apache-2.0 — Details →
5.16.1 18 Apr 2024 none Apache-2.0 — Details →
5.16.0 18 Apr 2024 none Apache-2.0 — Details →
5.15.2 15 Apr 2024 none Apache-2.0 — Details →
5.15.1 11 Apr 2024 none Apache-2.0 — Details →
5.15.0 10 Apr 2024 none Apache-2.0 — Details →
5.14.0 08 Apr 2024 none Apache-2.0 — Details →
5.13.0 29 Mar 2024 none Apache-2.0 — Details →
5.12.3 27 Mar 2024 none Apache-2.0 — Details →
5.12.2 26 Mar 2024 none Apache-2.0 — Details →
5.12.1 26 Mar 2024 none Apache-2.0 — Details →
5.12.0 13 Mar 2024 none Apache-2.0 — Details →
5.11.10 06 Mar 2024 none Apache-2.0 — Details →
5.11.9 04 Mar 2024 none Apache-2.0 — Details →
5.11.8 23 Feb 2024 none Apache-2.0 — Details →
5.11.7 16 Feb 2024 none Apache-2.0 — Details →
5.11.6 15 Feb 2024 none Apache-2.0 — Details →
5.11.5 15 Feb 2024 none Apache-2.0 — Details →
5.11.4 14 Feb 2024 none Apache-2.0 — Details →
5.11.3 07 Feb 2024 none — — Details →
5.11.2 29 Jan 2024 none — — Details →
5.11.1 26 Jan 2024 none — — Details →
5.11.0 08 Jan 2024 none — — Details →
5.10.5 14 Dec 2023 none — — Details →
5.10.4 14 Dec 2023 none — — Details →
5.10.3 22 Nov 2023 none — — Details →
5.10.2 22 Nov 2023 none — — Details →
5.10.1 20 Nov 2023 none — — Details →
5.10.0 15 Nov 2023 none — — Details →
5.9.4 13 Nov 2023 none — — Details →
5.9.3 09 Nov 2023 none — — Details →
5.9.2 08 Nov 2023 none — — Details →
5.9.1 25 Oct 2023 none — — Details →
5.9.0 29 Sep 2023 none — — Details →
5.8.0 29 Sep 2023 none — — Details →
5.7.2 18 Sep 2023 none — — Details →
5.7.1 14 Sep 2023 none — — Details →
5.7.0 13 Sep 2023 none — — Details →
5.6.2 06 Sep 2023 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 2
  • 2020 9
  • 2021 2
  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for swagger-ui

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-17495: Cross-site scripting in Swagger-UI 9.8 critical 3.23.11 15 Oct 2019
Cross-Site Scripting Vulnerability in swagger-ui 6.5 medium 3.0.13 11 Sep 2020
Cross-Site Scripting Vulnerability in swagger-ui 6.5 medium 3.20.9 11 Sep 2020
Improper Neutralization of Input During Web Page Generation in swagger-ui 6.1 medium 2.2.1 24 May 2022
CVE-2018-25031: Spoofing attack in swagger-ui 4.3 medium 4.1.3 12 Mar 2022

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 swagger-ui

Is swagger-ui safe to use?

Vulert records 15 vulnerabilities for swagger-ui in npm: 4 critical, 1 high, 10 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 swagger-ui's Vulert package health score?

Vulert scores swagger-ui 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 swagger-ui affected?

No. 5.34.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 swagger-ui have?

15 vulnerabilities are recorded for swagger-ui in the npm ecosystem: 4 critical, 1 high, 10 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 swagger-ui vulnerabilities disclosed?

0 vulnerabilities were recorded for swagger-ui in the last 12 months, and the oldest entry in this database dates to 20 Jun 2019. 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 swagger-ui 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 swagger-ui for upcoming vulnerabilities?

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