CVE-2026-27614: Bugsink is a self-hosted error tracking tool

Q: How do I fix CVE-2026-27614?

bugsink: upgrade to 2.0.13. Exact commands for each OS are on this page.

Q: Is CVE-2026-27614 being exploited?

CVE-2026-27614 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-27614 affect?

CVE-2026-27614 affects bugsink. Severity is critical (CVSS 9.3). Bugsink is a self-hosted error tracking tool. In versions prior to 2.0.13, an unauthenticated attacker who can submit events to a Bugsink project can store arbitrary JavaScript in an event. The payload executes only if a user explicitly vie

Q: How urgent is CVE-2026-27614?

Priority 44/100. Critical severity; Public exploit reference

This month

CRITICAL 9.3UPGRADE

CVE-2026-27614 is a critical-severity flaw (CVSS 9.3) affecting bugsink. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Bugsink is a self-hosted error tracking tool. In versions prior to 2.0.13, an unauthenticated attacker who can submit events to a Bugsink project can store arbitrary JavaScript in an event. The payload executes only if a user explicitly views the affected Stacktrace in the web UI. When Pygments returns more lines than it was given (a known upstream quirk that triggers with Ruby heredoc-style input), `_pygmentize_lines()` in `theme/templatetags/is

Why this priority

Critical severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	9.3 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 73%)
CISA exploited list	No
Weakness	CWE-79
Published	2026-02-25
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: bugsink

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-02-25 03:16 UTCPublished CVE record published
2026-06-17 10:27 UTCUpdated Record last modified

bugsink bugsink UPGRADE

Affected: < 2.0.13

Fixed in: 2.0.13

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy bugsink || rpm -q bugsink || bugsink --version

2. UPGRADE to 2.0.13 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade bugsink

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade bugsink

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-27614?

bugsink: upgrade to 2.0.13. Exact commands for each OS are on this page.

Is CVE-2026-27614 being exploited?

CVE-2026-27614 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-27614 affect?

CVE-2026-27614 affects bugsink. Severity is critical (CVSS 9.3). Bugsink is a self-hosted error tracking tool. In versions prior to 2.0.13, an unauthenticated attacker who can submit events to a Bugsink project can store arbitrary JavaScript in an event. The payload executes only if a user explicitly vie

How urgent is CVE-2026-27614?

Priority 44/100. Critical severity; Public exploit reference

Software pages

Ruby vulnerabilities

References

← Back to latest CVEs