Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Webhook Authorization Header Returned in Plaintext via API

cve-program · severity unknownEUVD CVSS 3.1 2.7 CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary 2.7 LOWCVSS_V3 Publisher rating LOWFixed by code.gitea.io/gitea 1.27.0osv · severity unknownFixed by gitea.dev 1.27.0KEV status unknown

cve-program · CVE-2026-58511

Published

Webhook Authorization Header Returned in Plaintext via API

Read the publisher's advisory

euvd · EUVD-2026-58124

Published

Webhook Authorization Header Returned in Plaintext via API

Read the publisher's advisory

nvd · CVE-2026-58511

Published

Webhook Authorization Header Returned in Plaintext via API

Read the publisher's advisory

osv · GHSA-3r5c-2xxx-h872

Published

## Summary The `ToHook()` function in `services/webhook/general.go` decrypts the webhook's `HeaderAuthorizationEncrypted` field and returns the plaintext authorization header in the API response. Any repository admin can read the full plaintext value of webhook authorization headers (Bearer tokens, Basic auth credentials, API keys) set by other admins. The authorization header is stored encrypted in the database using the server's `SecretKey`, but `ToHook()` decrypts it before serializing it into the API response — converting a write-only secret into a readable credential. ## Vulnerable Code **File:** `services/webhook/general.go:407-420` ```go func ToHook(repoLink string, w *webhook_model.Webhook) (*api.Hook, error) { // ... authorizationHeader, err := w.HeaderAuthorization() // DECRYPTS from DB if err != nil { return nil, err } return &api.Hook{ // ... AuthorizationHeader: authorizationHeader, // PLAINTEXT in response // ... }, nil } ``` **Decryption function:** `models/webhook/webhook.go:209-216` ```go func (w Webhook) HeaderAuthorization() (string, error) { if w.HeaderAuthorizationEncrypted == "" { return "", nil } return secret.DecryptSecret(setting.SecretKey, w.HeaderAuthorizationEncrypted) } ``` ## Affected Endpoints All call `ToHook()`: - `GET /api/v1/repos/{owner}/{repo}/hooks` (requires repo admin) - `GET /api/v1/repos/{owner}/{repo}/hooks/{id}` (requires repo admin) - `GET /api/v1/admin/hooks` (requires site admin) - `GET /api/v1/orgs/{org}/hooks` (requires org admin) - `GET /api/v1/user/hooks` (requires authenticated user) ## Steps to Reproduce 1. Admin A creates a webhook with a sensitive authorization header. 2. Admin B (different repo admin) lists webhooks via `GET /api/v1/repos/{owner}/{repo}/hooks`. 3. The API response includes the full plaintext authorization header set by Admin A. ## Impact - Cross-admin secret exposure on shared repositories - Credential harvesting if a repo admin's Gitea token is stolen - External service compromise via leaked Bearer tokens and API keys - Undermines the intentional encryption-at-rest protection ## Suggested Fix The authorization header should be write-only. Return a masked/redacted version or a boolean `has_authorization_header` flag instead. ## References - Vulnerable function: `services/webhook/general.go:392-425` - Decryption function: `models/webhook/webhook.go:209-216` - Verified against commit 19f0169

Read the publisher's advisory

osv · GO-2026-6040

Published

Gitea: Webhook Authorization Header Returned in Plaintext via API in gitea.dev

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).

Advisory history

16 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

9 Nov 2026 14:07:10 UTC

Webhook Authorization Header Returned in Plaintext via API

euvd · EUVD-2026-58124 · Published

7 Nov 2026 13:24:34 UTC

Webhook Authorization Header Returned in Plaintext via API

euvd · EUVD-2026-58124 · Published

5 Nov 2026 12:41:35 UTC

Webhook Authorization Header Returned in Plaintext via API

euvd · EUVD-2026-58124 · Published

3 Nov 2026 12:00:26 UTC

Webhook Authorization Header Returned in Plaintext via API

euvd · EUVD-2026-58124 · Published

1 Nov 2026 11:23:30 UTC

Webhook Authorization Header Returned in Plaintext via API

euvd · EUVD-2026-58124 · Published

24 Oct 2026 13:19:41 UTC

Gitea: Webhook Authorization Header Returned in Plaintext via API

osv · GHSA-3r5c-2xxx-h872 · Published

24 Oct 2026 13:19:41 UTC

Gitea: Webhook Authorization Header Returned in Plaintext via API in gitea.dev

osv · GO-2026-6040 · Published

23 Oct 2026 15:48:27 UTC

Webhook Authorization Header Returned in Plaintext via API

cve-program · CVE-2026-58511 · Published

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 21 Nov 03:30 UTC · 274 of 275 readable · 270 fully read · documentation 457/469 current