VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

io.swagger:swagger-codegen: vulnerability history, versions and safety

io.swagger:swagger-codegen is a package in the Maven ecosystem. Vulert records 3 vulnerabilities for it across 31 releases, from Oct 2018 to Mar 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 M1 L1
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 io.swagger:swagger-codegen vulnerabilities

Vulert verdict on io.swagger:swagger-codegen 3.0.0-rc1 i

Updated on 23 Oct 2026

Good news: 3.0.0-rc1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 65/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Moderate

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

  • Current release 3.0.0-rc1 — unaffected i
  • Vulnerabilities on record 3 over 2 years · 0 in the last year i
  • Latest disclosure 11 Mar 2021 i
  • Highest CVSS 9.3 i
  • With no published fix 0 i
  • Depended on by 13 packages i
  • Stars 17,793 i
  • OpenSSF scorecard 3/10 i
  • Last release 100 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, 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 io.swagger:swagger-codegen, 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
2.4.53 22 Oct 2026 none Apache-2.0 — Details →
2.4.52 15 Apr 2026 none Apache-2.0 — Details →
2.4.51 12 Mar 2026 none Apache-2.0 — Details →
2.4.50 24 Nov 2025 none Apache-2.0 — Details →
2.4.49 28 Oct 2025 none Apache-2.0 — Details →
2.4.48 29 Sep 2025 none Apache-2.0 — Details →
2.4.47 16 Sep 2025 none Apache-2.0 — Details →
2.4.46 30 Jun 2025 none Apache-2.0 — Details →
2.4.45 06 Jun 2025 none Apache-2.0 — Details →
2.4.44 18 Dec 2024 none Apache-2.0 — Details →
2.4.43 09 Aug 2024 none Apache-2.0 — Details →
2.4.42 29 Jul 2024 none Apache-2.0 — Details →
2.4.41 22 Apr 2024 none Apache-2.0 — Details →
2.4.40 22 Apr 2024 none Apache-2.0 — Details →
2.4.39 02 Jan 2024 none Apache-2.0 — Details →
2.4.38 29 Dec 2023 none Apache-2.0 — Details →
2.4.37 21 Nov 2023 none Apache-2.0 — Details →
2.4.36 26 Oct 2023 none Apache-2.0 — Details →
2.4.35 26 Oct 2023 none Apache-2.0 — Details →
2.4.34 19 Oct 2023 none Apache-2.0 — Details →
2.4.33 02 Oct 2023 none Apache-2.0 — Details →
2.4.32 17 May 2023 none Apache-2.0 — Details →
2.4.31 02 Apr 2023 none Apache-2.0 — Details →
2.4.30 16 Feb 2023 none Apache-2.0 — Details →
2.4.29 10 Nov 2022 none Apache-2.0 — Details →
2.4.28 15 Aug 2022 none Apache-2.0 — Details →
2.4.27 12 Apr 2022 none Apache-2.0 — Details →
2.4.26 07 Feb 2022 none Apache-2.0 — Details →
2.4.25 28 Dec 2021 none Apache-2.0 — Details →
2.4.24 18 Nov 2021 none Apache-2.0 — Details →
2.4.23 08 Oct 2021 none Apache-2.0 — Details →
2.4.22 30 Sep 2021 none Apache-2.0 — Details →
2.4.21 28 Jun 2021 none Apache-2.0 — Details →
2.4.20 29 May 2021 none Apache-2.0 — Details →
2.4.19 03 Mar 2021 none Apache-2.0 — Details →
2.4.18 29 Dec 2020 M1 L1 Apache-2.0 Yes Details →
2.4.17 01 Nov 2020 M1 L1 Apache-2.0 Yes Details →
2.4.16 04 Oct 2020 M1 L1 Apache-2.0 Yes Details →
2.4.15 28 Jul 2020 M1 L1 Apache-2.0 Yes Details →
2.4.14 16 May 2020 M1 L1 Apache-2.0 Yes Details →
2.4.13 02 Apr 2020 M1 L1 Apache-2.0 Yes Details →
2.4.12 15 Jan 2020 M1 L1 Apache-2.0 Yes Details →
2.4.11 03 Jan 2020 M1 L1 Apache-2.0 Yes Details →
2.4.10 16 Nov 2019 M1 L1 Apache-2.0 Yes Details →
2.4.9 14 Oct 2019 M1 L1 Apache-2.0 Yes Details →
2.4.8 23 Aug 2019 M1 L1 Apache-2.0 Yes Details →
2.4.7 11 Jul 2019 M1 L1 Apache-2.0 Yes Details →
2.4.6 27 Jun 2019 M1 L1 Apache-2.0 Yes Details →
2.4.5 25 Apr 2019 M1 L1 Apache-2.0 Yes Details →
2.4.4 26 Mar 2019 M1 L1 Apache-2.0 Yes Details →
2.4.3 25 Mar 2019 M1 L1 Apache-2.0 Yes Details →
2.4.2 18 Feb 2019 M1 L1 Apache-2.0 Yes Details →
2.4.1 15 Jan 2019 M1 L1 Apache-2.0 Yes Details →
2.4.0 30 Nov 2018 M1 L1 Apache-2.0 Yes Details →
3.0.0-rc1 29 May 2018 none Apache-2.0 — Details →
3.0.0-rc0 25 Jan 2018 none Apache-2.0 — Details →
2.3.1 17 Jan 2018 M1 L1 Apache-2.0 Yes Details →
2.3.0 22 Dec 2017 M1 L1 Apache-2.0 Yes Details →
2.2.3 15 Jul 2017 M1 L1 Apache-2.0 Yes Details →
2.2.2 01 Mar 2017 M1 L1 Apache-2.0 Yes Details →
2.2.1 08 Aug 2016 H1 M1 L1 Apache-2.0 Yes Details →
2.2.0 17 Jul 2016 H1 M1 L1 Apache-2.0 Yes Details →
2.1.6 06 Apr 2016 H1 M1 L1 Apache-2.0 Yes Details →
2.1.5 06 Jan 2016 H1 M1 L1 Apache-2.0 Yes Details →
2.1.4 26 Oct 2015 H1 M1 L1 Apache-2.0 Yes Details →
2.1.3 24 Aug 2015 H1 M1 L1 Apache-2.0 Yes Details →
2.1.2 09 Jun 2015 H1 M1 L1 Apache-2.0 Yes Details →
2.1.1 08 Jun 2015 H1 M1 L1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2021 2

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

03 Vulnerabilities

Recorded vulnerabilities for io.swagger:swagger-codegen

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-21363: Local Privilege Escalation Vulnerability in io.swagger:swagger-codegen 9.3 low 2.4.19 11 Mar 2021
CVE-2017-1000208: Deserialization of Untrusted Data in swagger-parser 8.8 high 2.2.2 19 Oct 2018
CVE-2021-21364: Local Information Disclosure Vulnerability in io.swagger:swagger-codegen 6.2 medium 2.4.19 11 Mar 2021

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 io.swagger:swagger-codegen

Is io.swagger:swagger-codegen safe to use?

Vulert records 3 vulnerabilities for io.swagger:swagger-codegen in Maven: 0 critical, 1 high, 1 medium and 1 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 io.swagger:swagger-codegen's Vulert package health score?

Vulert scores io.swagger:swagger-codegen 65/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 io.swagger:swagger-codegen affected?

No. 3.0.0-rc1, 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.

Which version of io.swagger:swagger-codegen should I use?

3.0.0-rc1 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 io.swagger:swagger-codegen have?

3 vulnerabilities are recorded for io.swagger:swagger-codegen in the Maven ecosystem: 0 critical, 1 high, 1 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new io.swagger:swagger-codegen vulnerabilities disclosed?

0 vulnerabilities were recorded for io.swagger:swagger-codegen in the last 12 months, and the oldest entry in this database dates to 19 Oct 2018. 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 io.swagger:swagger-codegen 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 io.swagger:swagger-codegen for upcoming vulnerabilities?

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