# Gogs's Unauthenticated Jupyter Notebook (ipynb) Sanitizer allows arbitrary data: URIs leading to XSS

Advisory record · `GHSA-3w28-36p9-w929`

- **Identifiers:** `GHSA-3w28-36p9-w929` · `CVE-2026-52816` · `GO-2026-5103`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html) · [CWE-80](https://cwe.mitre.org/data/definitions/80.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md)
- **Published:** 23 Jun 2026
- **Updated:** 21 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 Jun 2026, 17:33 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `gogs.io/gogs` (Go): affected `<0.14.3`; fixed in `0.14.3`

## Machine-written summary

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

> The Go package gogs.io/gogs is vulnerable in versions before 0.14.3. Its Jupyter Notebook sanitizer endpoint (POST /-/api/sanitize_ipynb) accepts arbitrary data: URIs, including data:text/html, so a registered user can get attacker-controlled HTML and JavaScript back in the sanitized output, which can lead to cross-site scripting. Upgrade to version 0.14.3, which contains the fix. The source gives no workaround other than the fix.

Written 6 Nov 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

- 5.4 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N/E:P`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0068, the 52nd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:05 UTC: First seen by agentprime
- 31 Oct 2026, 15:05 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3w28-36p9-w929)

## Sources

- [GitHub Advisory Database: GHSA-3w28-36p9-w929](https://github.com/advisories/GHSA-3w28-36p9-w929)
- [OSV: GHSA-3w28-36p9-w929](https://osv.dev/vulnerability/GHSA-3w28-36p9-w929)
- <https://github.com/gogs/gogs/security/advisories/GHSA-3w28-36p9-w929>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-52816>
- <https://github.com/gogs/gogs/pull/8326>
- <https://github.com/gogs/gogs/commit/dd1bd9837aa196b3ed3a8ee21e5727b5d7a986a3>
- <https://github.com/gogs/gogs>
- <https://github.com/gogs/gogs/releases/tag/v0.14.3>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-3w28-36p9-w929>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3w28-36p9-w929/>. Everything for agents: <https://agentprime.io/llms.txt>.
