VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

sanic: vulnerability history, versions and safety

sanic is a package in the PyPI ecosystem. Vulert records 7 vulnerabilities for it across 89 releases, from Nov 2017 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded H3 M1 U3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 01 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all sanic vulnerabilities

Vulert verdict on sanic 25.12.1 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 25.12.1 — unaffected i
  • Vulnerabilities on record 7 over 8 years · 3 in the last year i
  • Latest disclosure 01 Oct 2026 i
  • Highest CVSS 8.3 i
  • With no published fix 0 i
  • Depended on by 252 packages i
  • Stars 18,642 i
  • OpenSSF scorecard 4/10 i
  • Last release 4 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, 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 sanic, 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
25.12.1 31 May 2026 none MIT — Details →
24.12.1 31 May 2026 none MIT — Details →
25.12.0 31 Dec 2025 U1 MIT Yes Details →
25.3.0 31 Mar 2025 none MIT — Details →
24.12.0 31 Dec 2024 M1 U1 MIT Yes Details →
24.6.0 30 Jun 2024 M1 U1 MIT Yes Details →
23.12.2 30 Jun 2024 M1 U1 MIT Yes Details →
23.12.1 09 Jan 2024 M1 U1 MIT Yes Details →
23.12.0 31 Dec 2023 M1 U1 MIT Yes Details →
23.6.0 25 Jul 2023 M1 U1 MIT Yes Details →
23.3.0 26 Mar 2023 M1 U1 MIT Yes Details →
22.12.0 27 Dec 2022 M1 U1 MIT Yes Details →
22.9.1 31 Oct 2022 M1 U1 MIT Yes Details →
22.9.0 29 Sep 2022 M1 U1 MIT Yes Details →
22.6.2 11 Aug 2022 M1 U1 MIT Yes Details →
22.6.1 31 Jul 2022 M1 U1 MIT Yes Details →
21.12.2 31 Jul 2022 M1 U1 MIT Yes Details →
20.12.7 31 Jul 2022 M1 U1 MIT Yes Details →
22.6.0 30 Jun 2022 H1 M1 U2 MIT Yes Details →
22.3.2 11 May 2022 H1 M1 U2 MIT Yes Details →
22.3.1 17 Apr 2022 H1 M1 U2 MIT Yes Details →
22.3.0 31 Mar 2022 H1 M1 U2 MIT Yes Details →
20.12.6 16 Feb 2022 M1 U2 MIT Yes Details →
20.12.5 16 Jan 2022 H1 M1 U2 MIT Yes Details →
21.12.1 06 Jan 2022 M1 U2 MIT Yes Details →
21.12.0 26 Dec 2021 M1 U2 MIT Yes Details →
21.9.3 21 Nov 2021 M1 U2 MIT Yes Details →
21.9.2 21 Nov 2021 M1 U2 MIT Yes Details →
21.9.1 02 Oct 2021 M1 U2 MIT Yes Details →
20.12.4 02 Oct 2021 H1 M1 U2 MIT Yes Details →
21.9.0 30 Sep 2021 M1 U2 MIT Yes Details →
21.6.2 02 Aug 2021 M1 U2 MIT Yes Details →
21.6.1 28 Jul 2021 M1 U2 MIT Yes Details →
21.6.0 27 Jun 2021 M1 U2 MIT Yes Details →
21.3.4 19 Apr 2021 M1 U2 MIT Yes Details →
21.3.2 23 Mar 2021 M1 U2 MIT Yes Details →
21.3.1 21 Mar 2021 M1 U2 MIT Yes Details →
21.3.0 21 Mar 2021 M1 U2 MIT Yes Details →
20.12.3 21 Mar 2021 H1 M1 U2 MIT Yes Details →
20.12.2 16 Feb 2021 H1 M1 U2 MIT Yes Details →
19.12.5 16 Feb 2021 H1 M1 U2 MIT Yes Details →
20.12.1 05 Jan 2021 H1 M1 U2 MIT Yes Details →
20.12.0 28 Dec 2020 H1 M1 U2 MIT Yes Details →
19.12.4 05 Nov 2020 H1 M1 U2 MIT Yes Details →
20.9.1 25 Oct 2020 H1 M1 U2 MIT Yes Details →
19.12.3 25 Oct 2020 H1 M1 U2 MIT Yes Details →
20.9.0 30 Sep 2020 H1 M1 U2 MIT Yes Details →
20.6.3 29 Jun 2020 H1 M1 U2 MIT Yes Details →
20.6.2 29 Jun 2020 H1 M1 U2 MIT Yes Details →
20.6.1 28 Jun 2020 H1 M1 U2 MIT Yes Details →
20.6.0 28 Jun 2020 H1 M1 U2 MIT Yes Details →
20.3.0 14 May 2020 H1 M1 U2 MIT Yes Details →
19.12.2 02 Jan 2020 H1 M1 U2 MIT Yes Details →
19.12.0 27 Dec 2019 H1 M1 U2 MIT Yes Details →
19.9.0 12 Oct 2019 H1 M1 U2 MIT Yes Details →
19.6.3 22 Aug 2019 H1 M1 U2 MIT Yes Details →
19.6.2 08 Jul 2019 H1 M1 U2 MIT Yes Details →
19.6.0 21 Jun 2019 H1 M1 U2 MIT Yes Details →
19.3.1 23 Mar 2019 H1 M1 U2 MIT Yes Details →
18.12.0 27 Dec 2018 H1 M1 U2 MIT Yes Details →
0.8.3 13 Sep 2018 H1 M1 U2 MIT Yes Details →
0.8.2 13 Sep 2018 H1 M1 U2 MIT Yes Details →
0.8.1 06 Sep 2018 H1 M1 U2 MIT Yes Details →
0.8.0 06 Sep 2018 H1 M1 U2 MIT Yes Details →
0.7.0 06 Dec 2017 H1 M1 U2 MIT Yes Details →
0.6.0 03 Aug 2017 H1 M1 U2 MIT Yes Details →
0.5.4 09 May 2017 H1 M1 U2 MIT Yes Details →
0.5.2 09 May 2017 H1 M1 U2 MIT Yes Details →
0.5.1 14 Apr 2017 H1 M1 U2 MIT Yes Details →
0.5.0 11 Apr 2017 H2 M1 U3 MIT Yes Details →
0.4.1 28 Feb 2017 H2 M1 U3 MIT Yes Details →
0.4.0 25 Feb 2017 H2 M1 U3 MIT Yes Details →
0.3.1 09 Feb 2017 H2 M1 U3 MIT Yes Details →
0.3.0 28 Jan 2017 H2 M1 U3 MIT Yes Details →
0.2.0 14 Jan 2017 H2 M1 U3 MIT Yes Details →
0.1.9 25 Dec 2016 H2 M1 U3 MIT Yes Details →
0.1.8 29 Nov 2016 H2 M1 U3 MIT Yes Details →
0.1.7 25 Oct 2016 H2 M1 U3 MIT Yes Details →
0.1.6 25 Oct 2016 H1 M1 U3 MIT Yes Details →
0.1.5 23 Oct 2016 H1 M1 U3 MIT Yes Details →
0.1.4 18 Oct 2016 H1 M1 U3 MIT Yes Details →
0.1.3 16 Oct 2016 H1 M1 U3 MIT Yes Details →
0.1.1 15 Oct 2016 H1 M1 U3 non-standard Yes Details →
0.1.0 15 Oct 2016 H1 M1 U3 non-standard Yes Details →
0.1.3-py3.5 — H1 M1 U3 — Yes Details →
0.1.4-py3.5 — H1 M1 U3 — Yes Details →
0.1.5-py3.5 — H1 M1 U3 — Yes Details →
0.1.6-py3.5 — H1 M1 U3 — Yes Details →
0.1.7-py3.5 — H2 M1 U3 — Yes Details →
0.1.8-py3.5 — H2 M1 U3 — Yes Details →
0.1.9-py3.5 — H2 M1 U3 — Yes Details →
0.1.9-py3.6 — H2 M1 U3 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2022 3
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for sanic

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-35920: Sanic - Path Traversal Vulnerability 8.3 high 22.6.1 06 Aug 2022
CVE-2022-35920: Sanic Path Traversal Vulnerability via Encoded URLs 8.3 high 20.12.7 06 Jul 2026
CVE-2017-16762: Sanic Arbitrary File Read and Directory Traversal 7.5 high 0.5.1 17 May 2022
CVE-2026-85078: Sanic Chunked Trailer Request Smuggling Vulnerability 6.5 medium 24.12.1 17 Sep 2026
CVE-2026-85078: Sanic HTTP/1.1 Chunked Trailer Request Smuggling Vulnerability 6.5 medium 24.12.1 01 Oct 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 sanic

Is sanic safe to use?

Vulert records 7 vulnerabilities for sanic in PyPI: 0 critical, 3 high, 1 medium and 0 low, plus 3 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is sanic's Vulert package health score?

Vulert scores sanic 76/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 sanic affected?

No. 25.12.1, 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 sanic should I use?

25.12.1 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 sanic have?

7 vulnerabilities are recorded for sanic in the PyPI ecosystem: 0 critical, 3 high, 1 medium and 0 low, plus 3 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new sanic vulnerabilities disclosed?

3 vulnerabilities were recorded for sanic in the last 12 months, and the oldest entry in this database dates to 10 Nov 2017. 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 sanic 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 sanic for upcoming vulnerabilities?

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