CVE-2026-26022 Gogs: Stored XSS via data URI in issue comments

High 8.7 Published Updated

Authenticated users can inject arbitrary JavaScript via data URIs in issue comments, potentially leading to code execution or account takeover.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-26022?

CVE-2026-26022 is a high-severity cross-site scripting vulnerability in gogs, published on 5 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

Gogs is an open source self-hosted Git service. Prior to version 0.14.2, a stored cross-site scripting (XSS) vulnerability exists in the comment and issue description functionality. The application's HTML sanitizer explicitly allows data: URI schemes, enabling authenticated users to inject arbitrary JavaScript execution via malicious links. This issue has been patched in version 0.14.2.

Weakness: CWE-79

Which versions are affected by CVE-2026-26022?

3 open source packages ship an affected version, including gogs.io/gogs. It affects 1 product.

PackageAffectedFixed in
gogs.io/gogs GoAll versionsNone
gogs.io/gogs GoAll versions0.14.2
gogs.io/gogs GoAll versions0.14.2

Products include Gogs Gogs.

How do I fix CVE-2026-26022?

Upgrade gogs.io/gogs to 0.14.2 or later.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2026-26022 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26022 exists.

Sources

Also known as GHSA-xrcr-gmf5-2r8j, GO-2026-4620.

Is CVE-2026-26022 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free