@tdurieux/anonymous_github Vulnerable to XSS via Unsanitized GitHub Repository Content Rendering in Anonymous GitHub
Affects @tdurieux/anonymous_githubSource GCVE Database
CVSS 8.1 High : upgrade to 2.3.0 soon.
Data as of 27 Oct 2026, 01:44 UTC
- Patch
- Available – fixed in 2.3.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NWhat to do
Upgrade @tdurieux/anonymous_github to 2.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@tdurieux/anonymous_github | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in version 2.3.0 of @tdurieux/anonymous_github. Users and administrators should upgrade to this version to remediate the vulnerability. The recommended remediation includes sanitizing markdown output with DOMPurify before rendering, avoiding the use of $sce.trustAsHtml() without proper sanitization, serving HTML content with Content-Disposition headers or sandboxed iframes, escaping filenames and paths in templates, and implementing Content Security Policy headers. Until the upgrade is applied, users should avoid anonymizing or viewing untrusted repositories on the platform.
Description
Anonymous GitHub fetches and renders GitHub repository README markdown content without sanitization, using the 'marked' library with sanitization disabled and AngularJS's $sce.trustAsHtml() to inject HTML. This allows an attacker to craft a malicious README that executes arbitrary JavaScript in the Anonymous GitHub origin, leading to stored cross-site scripting (XSS). The vulnerability can result in account takeover, theft of authentication tokens, and data exfiltration of user configurations and private repository data. A fix is available in version 2.3.0.