# CVE-2026-117677: Gitea Helm chart decompression denial of service

Source: https://junglewise.ai/threats/cve-2026-117677-when-parsing-an-uploaded-helm-chart-gitea-decompressed-the  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-01. Updated: 2026-11-01  
License: CC BY 4.0 with a link back

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

Gitea, a self-hosted Git platform, improperly decompresses uploaded Helm chart archives without limiting decompression size, checking quotas after decompression rather than before. An authenticated user with package write access could upload highly compressed archives that consume excessive CPU during decompression, degrading server availability, though no code execution or data exposure is possible.

Technologies: [Gitea](https://junglewise.ai/threats/technologies/gitea). Vendors: [Gitea](https://junglewise.ai/threats/vendors/gitea).

## Quick answers

**Is CVE-2026-117677 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-117677 being exploited in the wild.

**How severe is CVE-2026-117677?** Informational severity, published 1 November 2026.

**Which products and versions are affected?** Gitea prior to 28.3.0.

**Is there a fix for CVE-2026-117677?** 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-117677 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-117677?** 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

The vulnerability exists in Gitea's Helm chart parser, which decompresses tar archives to search for Chart.yaml without enforcing decompression size limits, and performs this decompression before the package size quota check. An attacker with package write access could exploit this via a bomb-style compressed archive (small compressed size, enormous decompressed size) to cause a denial of service through CPU exhaustion. The fix bounds how much of a Helm chart archive is inflated while parsing.

## Affected products

- Gitea Gitea prior to 28.3.0

## Timeline

- 2026-11-01: disclosed

## References

- [https://blog.gitea.com/release-of-28.3.0/](https://blog.gitea.com/release-of-28.3.0/)
- [https://github.com/go-gitea/gitea/pull/39942](https://github.com/go-gitea/gitea/pull/39942)

## Related threats

- [Gitea account takeover via OAuth2 auto-linking](https://junglewise.ai/threats/cve-2026-120263-when-oauth2-client-account-linking-is-set-to-auto-not-the)
- [Gitea limited-visibility profile disclosure via public-only token](https://junglewise.ai/threats/cve-2026-119627-the-web-profile-and-rss-atom-feed-routes-of-users-and)
- [Gitea token scope bypass in web routes](https://junglewise.ai/threats/cve-2026-119625-the-username-web-route-accepted-personal-access-tokens-over-http)
- [Gitea project boards information disclosure of private pull requests](https://junglewise.ai/threats/cve-2026-119533-repository-and-organization-project-boards-listed-the-pull)
- [Gitea API token scope bypass in repository deletion](https://junglewise.ai/threats/cve-2026-119441-delete-api-v1-orgs-org-repos-deletes-all-repositories-of-an)