Stored XSS via unescaped Pygments fallback
Published Feb 25, 2026 · Updated Feb 25, 2026
Stored XSS in Bugsink before 2.0.13 allows remote attackers to execute JavaScript in an administrator's browser via crafted events. When Pygments returns extra lines for Ruby heredoc-style input, _pygmentize_lines() returns raw event lines that mark_safe() then treats as HTML-safe. Exploitation requires a reachable ingest endpoint, a valid project DSN, and an administrator to view the crafted stacktrace, after which the script acts with that administrator's Bugsink privileges.
Summary
What happened
Stored XSS in Bugsink before 2.0.13 allows remote attackers to execute JavaScript in an administrator's browser via crafted events. When Pygments returns extra lines for Ruby heredoc-style input, _pygmentize_lines() returns raw event lines that mark_safe() then treats as HTML-safe. Exploitation requires a reachable ingest endpoint, a valid project DSN, and an administrator to view the crafted stacktrace, after which the script acts with that administrator's Bugsink privileges.
The record
- CVE
- CVE-2026-27614
- Published
- Feb 25, 2026
- Updated
- Feb 25, 2026
- Vendor
- Bugsink
- Product
- Bugsink
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 25, 2026CVE publishedPublication date reported by the CVE source.
- Feb 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.0.13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor advisory event-submission PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo