VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

bugsink: vulnerability history, versions and safety

bugsink is a package in the PyPI ecosystem. Vulert records 20 vulnerabilities for it across 61 releases, from Jul 2025 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
20 vulnerabilities recorded C1 H4 M3 L2 U10
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
19 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all bugsink vulnerabilities

Vulert verdict on bugsink 2.6.2 i

Updated on 22 Oct 2026

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

Package health score 63/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 2.6.2 — unaffected i
  • Vulnerabilities on record 20 over 1 year · 19 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 0 i
  • Stars 2,135 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, 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 bugsink, 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.6.2 22 Oct 2026 none — — Details →
2.6.1 25 Sep 2026 none — — Details →
2.6.0 15 Sep 2026 none — — Details →
2.5.1 31 Aug 2026 none — — Details →
2.5.0 22 Jul 2026 none — — Details →
2.4.0 10 Jul 2026 none — — Details →
2.3.1 30 Jun 2026 none — — Details →
2.3.0 23 Jun 2026 none — — Details →
2.2.2 04 Jun 2026 none — — Details →
2.2.1 22 May 2026 M1 U1 — Yes Details →
2.2.0 21 May 2026 M1 U1 — Yes Details →
2.1.3 02 May 2026 M2 L2 U4 — Yes Details →
2.1.2 11 Apr 2026 M3 L2 U5 — Yes Details →
2.1.1 09 Apr 2026 M3 L2 U5 — Yes Details →
2.1.0 04 Apr 2026 H1 M3 L2 U6 — Yes Details →
2.0.14 03 Mar 2026 M3 L2 U5 — Yes Details →
2.0.13 21 Feb 2026 M3 L2 U5 — Yes Details →
2.0.12 26 Jan 2026 C1 M3 L2 U6 — Yes Details →
2.0.11 20 Jan 2026 C1 M3 L2 U6 — Yes Details →
2.0.10 14 Jan 2026 C1 M3 L2 U6 — Yes Details →
2.0.9 13 Jan 2026 C1 M3 L2 U6 — Yes Details →
2.0.8 10 Jan 2026 C1 M3 L2 U6 — Yes Details →
2.0.7 06 Jan 2026 C1 M3 L2 U6 — Yes Details →
2.0.6 08 Nov 2025 C1 M3 L2 U6 — Yes Details →
2.0.5 08 Nov 2025 C1 H1 M3 L2 U7 — Yes Details →
2.0.4 09 Oct 2025 C1 H2 M3 L2 U8 — Yes Details →
2.0.3 05 Oct 2025 C1 H2 M3 L2 U8 — Yes Details →
2.0.2 22 Sep 2025 C1 H2 M3 L2 U8 — Yes Details →
2.0.1 16 Sep 2025 C1 H2 M3 L2 U8 — Yes Details →
2.0.0 16 Sep 2025 C1 H2 M3 L2 U8 — Yes Details →
2.0.0a1 05 Sep 2025 C1 H2 M3 L2 U8 — Yes Details →
1.7.6 01 Aug 2025 C1 H2 M3 L2 U8 — Yes Details →
1.7.5 31 Jul 2025 C1 H2 M3 L2 U8 — Yes Details →
1.5.5 29 Jul 2025 C1 H2 M3 L2 U8 — Yes Details →
1.6.4 29 Jul 2025 C1 H2 M3 L2 U8 — Yes Details →
1.4.3 29 Jul 2025 C1 H2 M3 L2 U8 — Yes Details →
1.7.4 29 Jul 2025 C1 H2 M3 L2 U8 — Yes Details →
1.7.3 17 Jul 2025 C1 H3 M3 L2 U9 — Yes Details →
1.7.2 17 Jul 2025 C1 H3 M3 L2 U9 — Yes Details →
1.7.1 10 Jul 2025 C1 H3 M3 L2 U9 — Yes Details →
1.7.0 09 Jul 2025 C1 H3 M3 L2 U9 — Yes Details →
1.6.3 27 Jun 2025 C1 H2 M3 L2 U9 — Yes Details →
1.6.2 19 Jun 2025 C1 H2 M3 L2 U9 — Yes Details →
1.6.1 11 Jun 2025 C1 H2 M3 L2 U9 — Yes Details →
1.6.0 10 Jun 2025 C1 H2 M3 L2 U9 — Yes Details →
1.5.4 12 May 2025 C1 H2 M3 L2 U9 — Yes Details →
1.5.3 07 May 2025 C1 H2 M3 L2 U9 — Yes Details →
1.5.2 06 May 2025 C1 H2 M3 L2 U9 — Yes Details →
1.5.1 24 Apr 2025 C1 H2 M3 L2 U9 — Yes Details →
1.5.0 14 Apr 2025 C1 H2 M3 L2 U9 — Yes Details →
1.4.2 01 Apr 2025 C1 H2 M3 L2 U9 — Yes Details →
1.4.1 17 Mar 2025 C1 H2 M3 L2 U9 non-standard Yes Details →
1.4.0 13 Mar 2025 C1 H2 M3 L2 U9 non-standard Yes Details →
1.3.0 20 Feb 2025 C1 H2 M3 L2 U9 non-standard Yes Details →
1.2.0 11 Feb 2025 C1 H2 M3 L2 U9 non-standard Yes Details →
1.1.2 29 Jan 2025 C1 H2 M3 L2 U9 non-standard Yes Details →
1.1.1 21 Jan 2025 C1 H2 M3 L2 U9 non-standard Yes Details →
1.1.0 15 Jan 2025 C1 H2 M3 L2 U9 non-standard Yes Details →
1.0.1 16 Dec 2024 C1 H2 M3 L2 U9 non-standard Yes Details →
1.0.0 03 Dec 2024 C1 H2 M3 L2 U9 non-standard Yes Details →
0.1.20 28 Nov 2024 C1 H2 M3 L2 U9 non-standard Yes Details →
0.1.19 22 Nov 2024 C1 H2 M3 L2 U9 non-standard Yes Details →
0.1.18 20 Nov 2024 C1 H2 M3 L2 U9 non-standard Yes Details →
0.1.17 15 Nov 2024 C1 H2 M3 L2 U9 non-standard Yes Details →
0.1.16 07 Nov 2024 C1 H2 M3 L2 U9 non-standard Yes Details →
0.1.15 07 Nov 2024 C1 H2 M3 L2 U9 non-standard Yes Details →
0.1.14 14 Oct 2024 C1 H2 M3 L2 U9 non-standard Yes Details →
0.1.13 09 Oct 2024 C1 H2 M3 L2 U9 non-standard Yes Details →
0.1.12 04 Oct 2024 C1 H2 M3 L2 U9 non-standard Yes Details →
0.0.1 21 Feb 2024 C1 H2 M3 L2 U9 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 3
  • 2026 17

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

03 Vulnerabilities

Recorded vulnerabilities for bugsink

The 5 most severe of 20 vulnerabilities recorded for this package

Search all 20 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-27614: Bugsink Vulnerable to Stored XSS via Pygments Fallback in Stacktrace Rendering 9.3 critical 2.0.13 25 Feb 2026
CVE-2026-27614: Bugsink Stored XSS Vulnerability via Pygments Fallback in Stacktrace Rendering 9.3 critical 2.0.13 29 Jun 2026
CVE-2025-64508: Bugsink Remote DoS Vulnerability via Crafted Brotli Input 7.5 high 2.0.5 07 Jul 2026
CVE-2025-64508: Bugsink Remote DoS Vulnerability via Crafted Brotli Input 7.5 high 2.0.5 13 Nov 2025
CVE-2025-64509: Bugsink Remote DoS Vulnerability via Crafted Brotli Input 7.5 high 2.0.6 13 Nov 2025

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 bugsink

Is bugsink safe to use?

Vulert records 20 vulnerabilities for bugsink in PyPI: 1 critical, 4 high, 3 medium and 2 low, plus 10 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 bugsink's Vulert package health score?

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

No. 2.6.2, 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 bugsink have?

20 vulnerabilities are recorded for bugsink in the PyPI ecosystem: 1 critical, 4 high, 3 medium and 2 low, plus 10 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 bugsink vulnerabilities disclosed?

19 vulnerabilities were recorded for bugsink in the last 12 months, and the oldest entry in this database dates to 29 Jul 2025. 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 bugsink 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 bugsink for upcoming vulnerabilities?

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