Is CVE-2026-113429 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-113429 being exploited in the wild.

How severe is CVE-2026-113429?

Informational severity, published 1 November 2026.

Is there a fix for CVE-2026-113429?

Yes: fixed in Gitea 28.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-113429 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-113429?

Check whether you run Gitea at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-113429: Gitea Actions artifact uploads stored Content-Encoding as Content-Type

CVE-2026-113429 · Severity: info · Published 2026-11-01

Gitea, a self-hosted Git service with CI/CD capabilities, stored untrusted HTTP headers in artifact metadata, allowing attackers to serve HTML pages through the Gitea domain. A user who can run CI jobs could upload an artifact that renders as HTML in a victim's browser, enabling session hijacking or administrator account takeover on public repositories.

Technologies: Gitea. Vendors: Gitea.

Quick answers

Is CVE-2026-113429 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-113429 being exploited in the wild.
How severe is CVE-2026-113429?: Informational severity, published 1 November 2026.
Which products and versions are affected?: Gitea Legacy (v1 to v3).
Is there a fix for CVE-2026-113429?: Yes: fixed in Gitea 28.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-113429 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-113429?: Check whether you run Gitea at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: Gitea 28.3.0

Technical details

Legacy artifact uploads (v1–v3) stored the request's Content-Encoding header directly into the Content-Type column, which was then served back to download requests. By crafting a malicious artifact with a Content-Encoding value like "text/html" or "video/" prefix, an attacker bypassed Content-Security-Policy sandbox restrictions and caused browsers to execute arbitrary JavaScript in the Gitea origin context. The fix restricts stored values to only the gzip marker and validates MIME types before applying special headers.

Affected products

Gitea Gitea Legacy (v1 to v3)

Timeline

2026-11-01: disclosed
2026-11-01: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.