Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-f2xf-7x3g-4272

PrivateBin has stored Cross-Side-Scripting (XSS) vulnerability in attachment download link via dangerous MIME types with required user-interaction

CVSS 4.3 MediumEPSS 0.0044 · 38th percentile

Published by the GitHub Advisory Database at 28 Aug 2026, 20:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
privatebin/privatebinPackagist<2.0.52.0.5
Identifiers
GHSA-f2xf-7x3g-4272 · CVE-2026-55696 · PKSA-ysv6-x4qh-fd9v
Weakness (CWE)
CWE-79 · CWE-80
Tags
Published
28 Aug 2026
Updated
28 Aug 2026

Machine-written summary

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

PrivateBin versions before 2.0.5 are vulnerable to stored cross-site scripting through the attachment download link, where a text/html or SVG attachment is served unsanitized. An anonymous attacker can craft a paste with such an attachment, and if a victim opens the download link in a new tab, attacker JavaScript runs in the PrivateBin origin; this requires file upload to be enabled (non-default) and a weakened or absent Content-Security-Policy. Upgrade to PrivateBin 2.0.5, which is the fixed version.

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
4.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0044, the 38th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:06 UTC First seen by agentprime
  2. 31 Oct 2026, 14:06 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.