Is CVE-2026-58511 exploited in the wild?

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

How severe is CVE-2026-58511?

Low severity, with a CVSS score of 3.1, published 21 July 2026.

Which products and versions are affected?

Gitea < 1.27.0; code.gitea.io/gitea (Go) < 1.27.0, SEMVER:introduced=0,fixed=1.27.0; gitea.dev (Go) SEMVER:introduced=0,fixed=1.27.0.

Is there a fix for CVE-2026-58511?

Yes. code.gitea.io/gitea (Go): upgrade to 1.27.0 or later; gitea.dev (Go): upgrade to 1.27.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-58511 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-58511?

Check whether you run Gitea, code.gitea.io/gitea (Go) or gitea.dev (Go) 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-58511: Gitea plaintext webhook authorization header exposure in API

Q: Which products and versions are affected?

Gitea < 1.27.0; code.gitea.io/gitea (Go) < 1.27.0, SEMVER:introduced=0,fixed=1.27.0; gitea.dev (Go) SEMVER:introduced=0,fixed=1.27.0.

Q: Is there a fix for CVE-2026-58511?

Yes. code.gitea.io/gitea (Go): upgrade to 1.27.0 or later; gitea.dev (Go): upgrade to 1.27.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-58511 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-58511?

Check whether you run Gitea, code.gitea.io/gitea (Go) or gitea.dev (Go) 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-58511 · Severity: low · CVSS 3.1 · Published 2026-07-21

Gitea is an open-source forge software package for hosting software development version control using Git. A vulnerability in the webhook management system allows repository administrators to view sensitive authorization headers, such as API keys and Bearer tokens, in plain text through the API. This could allow a malicious or compromised administrator to steal credentials used to authenticate with external services, potentially leading to unauthorized access to those third-party platforms.

Technologies: Gitea, code.gitea.io/gitea (Go), gitea.dev (Go). Vendors: Gitea, Go.

Quick answers

Is CVE-2026-58511 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-58511 being exploited in the wild.
How severe is CVE-2026-58511?: Low severity, with a CVSS score of 3.1, published 21 July 2026.
Which products and versions are affected?: Gitea < 1.27.0; code.gitea.io/gitea (Go) < 1.27.0, SEMVER:introduced=0,fixed=1.27.0; gitea.dev (Go) SEMVER:introduced=0,fixed=1.27.0.
Is there a fix for CVE-2026-58511?: Yes. code.gitea.io/gitea (Go): upgrade to 1.27.0 or later; gitea.dev (Go): upgrade to 1.27.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-58511 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-58511?: Check whether you run Gitea, code.gitea.io/gitea (Go) or gitea.dev (Go) 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

code.gitea.io/gitea (Go): upgrade to 1.27.0 or later
```
go get code.gitea.io/gitea@v1.27.0
```
gitea.dev (Go): upgrade to 1.27.0 or later
```
go get gitea.dev@v1.27.0
```

Technical details

An information exposure vulnerability exists in Gitea's webhook API due to improper handling of encrypted secrets. The `ToHook()` function in `services/webhook/general.go` calls `HeaderAuthorization()`, which decrypts the `HeaderAuthorizationEncrypted` field from the database using the server's `SecretKey`. This decrypted plaintext value is then serialized directly into the API response. An attacker with repository administrator privileges can call endpoints such as `GET /api/v1/repos/{owner}/{repo}/hooks` to retrieve plaintext Bearer tokens, Basic auth credentials, or API keys configured for webhooks. This vulnerability is patched in version 1.27.0 by ensuring the authorization header is treated as write-only.

Affected products

Gitea Gitea < 1.27.0

Identifiers

CVE-2026-58511
GHSA-3r5c-2xxx-h872
GO-2026-6040

Timeline

2026-07-13: disclosed
2026-07-13: patched: Fixed in version 1.27.0
2026-07-21: advisory

References

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