Advisory record · GHSA-vp6q-7m36-pq3w

Bugsink is vulnerable to Stored XSS via Pygments fallback in stacktrace rendering

CVSS 9.3 CriticalCriticalEPSS 0.0034 · 27th percentile

Critical, because:

  • CVSS score 9.3: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 25 Feb 2026, 16:06 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
bugsinkPyPI<2.0.132.0.13
Identifiers
GHSA-vp6q-7m36-pq3w · CVE-2026-27614 · PYSEC-2026-301
Weakness (CWE)
CWE-79
Published
25 Feb 2026
Updated
27 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The Bugsink package on PyPI, versions before 2.0.13, has a stored cross-site scripting flaw in stacktrace rendering. An attacker who can submit events to a project, using its DSN, can store JavaScript that runs in an administrator's browser when that administrator views the affected event in the web UI, letting the attacker act with that user's privileges. The fix is to upgrade to Bugsink 2.0.13.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.3 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0034, the 27th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.