Description
When OpenID sign-in is enabled, Gitea processes unauthenticated assertion parameters and sends an HTTP POST request to the caller-supplied OpenID provider endpoint during verification. An attacker controls the destination and much of the form body, allowing interaction with internal HTTP services reachable from the Gitea server. The response is not returned to the attacker, so the issue is blind SSRF; its impact depends on the services and network addresses the server can reach.
Published: 2026-10-14
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: Blind SSRF allowing internal network access
Action: Patch Immediately
AI Analysis

Impact

Gitea’s OpenID sign‑in flow improperly processes unauthenticated assertion parameters and, during verification, sends an HTTP POST to a caller‑supplied OpenID provider endpoint. An attacker can dictate the destination URL and much of the form body, enabling the server to initiate internal HTTP requests. Because the response is not returned to the attacker, the flaw is a blind SSRF. The impact is limited to the internal services that the Gitea instance can reach, but it can allow sensitive data exposure, lateral movement, or privilege escalation within the local network.

Affected Systems

Any Gitea installation that has OpenID sign‑in enabled is potentially affected. Specific version information is not listed, so all current releases should be inspected for the fix referenced in the advisory.

Risk and Exploitability

The CVSS score is not disclosed in the available data, but the EPSS score of 0.00168 indicates a very low exploitation probability, although the blind SSRF nature and lack of authentication requirements still make the potential impact high. The vulnerability is not listed in the CISA KEV catalog, but it remains exploitable by any actor with network access to the Gitea server. An attacker can choose any reachable internal address for the POST request, making the risk dependent on the internal topology. The likely attack vector is a remote attacker who can supply a forged OpenID assertion during the sign‑in process.

Generated by OpenCVE AI on October 15, 2026 at 20:00 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to a patched release that resolves the OpenID verification flaw; see the GitHub advisory for version details.
  • If an upgrade cannot be performed immediately, disable the OpenID sign‑in feature to eliminate the blind SSRF path.
  • Restrict outbound HTTP traffic from the Gitea server to a whitelist of trusted domains to limit the scope of potential SSRF exploitation.

Generated by OpenCVE AI on October 15, 2026 at 20:00 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 14 Oct 2026 15:00:00 +0000

Type Values Removed Values Added
Description When OpenID sign-in is enabled, Gitea processes unauthenticated assertion parameters and sends an HTTP POST request to the caller-supplied OpenID provider endpoint during verification. An attacker controls the destination and much of the form body, allowing interaction with internal HTTP services reachable from the Gitea server. The response is not returned to the attacker, so the issue is blind SSRF; its impact depends on the services and network addresses the server can reach.
Title Gitea blind SSRF through OpenID assertion verification
Weaknesses CWE-918
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Gitea

Published:

Updated: 2026-10-14T14:38:10.532Z

Reserved: 2026-08-24T20:45:09.301Z

Link: CVE-2026-78231

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2026-10-14T15:17:25.533

Modified: 2026-10-14T16:04:39.483

Link: CVE-2026-78231

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-15T20:15:16Z

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)