GHSA-G485-8J3V-P6X8

@tdurieux/anonymous_github Vulnerable to XSS via Unsanitized GitHub Repository Content Rendering in Anonymous GitHub Origin

1. Stored XSS: Any malicious GitHub repository can execute JavaScript in the Anonymous GitHub origin when a user anonymizes it or views its content
2. Account Takeover: Steal authentication tokens and session cookies
3. Data Exfiltration: Access other users' anonymization configurations and private repository data via /api/user and /api/repo/list

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

GHSA-G485-8J3V-P6X8 has a CVSS score of 8.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.3.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. Sanitize markdown output with DOMPurify before rendering (the dependency already exists but is unused)
2. Serve HTML files with Content-Disposition: attachment or in a sandboxed iframe on a separate origin
3. Replace $sce.trustAsHtml() with proper ngSanitize usage
4. HTML-escape filenames and paths in directory listing templates
5. Add Content Security Policy headers

1. What is GHSA-G485-8J3V-P6X8? GHSA-G485-8J3V-P6X8 is a high-severity cross-site scripting (XSS) vulnerability in @tdurieux/anonymous_github (npm), affecting versions = 2.2.0. It is fixed in 2.3.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is GHSA-G485-8J3V-P6X8? GHSA-G485-8J3V-P6X8 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @tdurieux/anonymous_github are affected by GHSA-G485-8J3V-P6X8? @tdurieux/anonymous_github (npm) versions = 2.2.0 is affected.
4. Is there a fix for GHSA-G485-8J3V-P6X8? Yes. GHSA-G485-8J3V-P6X8 is fixed in 2.3.0. Upgrade to this version or later.
5. Is GHSA-G485-8J3V-P6X8 exploitable, and should I be worried? Whether GHSA-G485-8J3V-P6X8 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-G485-8J3V-P6X8 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-G485-8J3V-P6X8? Upgrade @tdurieux/anonymous_github to 2.3.0 or later.