Security readout for executives and security teams
Plain-English summary
CVE-2026-20904 is a Gitea access-control flaw affecting OpenID identity visibility settings. A logged-in user may be able to change visibility settings for another user’s OpenID URI. This is not described as code execution or data theft, but it can undermine account privacy, identity integrity, and trust in user profile controls.
Executive priority
Treat as a medium-priority integrity issue. It is unlikely to drive emergency response absent exploitation evidence, but it affects identity controls in developer infrastructure. Patch during the next prioritized maintenance window, sooner for public or broadly accessible Gitea deployments.
Technical view
Gitea fails to properly validate ownership when toggling OpenID URI visibility. The issue maps to broken access control/IDOR patterns, including CWE-284 and CWE-639. CVSS 3.1 is 6.5: network-accessible, low complexity, authenticated attacker, no user interaction, unchanged scope, high integrity impact, no confidentiality or availability impact.
Likely exposure
Exposure is most relevant to Gitea Open Source Git Server deployments where users authenticate and have OpenID identities configured. The provided CVE data does not clearly state an affected version range beyond vendor references to patch PRs and the v1.25.4 release, so teams should confirm applicability against the vendor advisory.
Exploitation context
No CISA KEV listing or provided source indicates active exploitation. Exploitation requires an authenticated account and targets another user’s OpenID visibility setting. The business impact is unauthorized modification of identity-related profile state rather than full system compromise, based on the available sources.
Researcher notes
The source bundle identifies patch PRs #36346 and #36361 and release v1.25.4, but the affected-version data appears incomplete or ambiguous. Researchers should rely on the vendor advisory for exact version applicability and avoid assuming broader product impact beyond Gitea OpenID visibility handling.
Mitigation direction
- Review the Gitea security advisory for affected-version details.
- Upgrade to Gitea v1.25.4 or another vendor-designated fixed release.
- Prioritize internet-facing or self-registration-enabled Gitea instances.
- Limit untrusted account creation until patched, if operationally feasible.
- Monitor vendor guidance for follow-up fixes or clarifications.
Validation and detection
- Inventory all Gitea instances and record running versions.
- Check whether OpenID identity features are used.
- Confirm the instance is upgraded to a vendor-fixed release.
- Review logs for unexpected OpenID visibility changes.
- Track remediation evidence against the Gitea advisory and release notes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-20904 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security AdvisoryCVE reference · vendor-advisory
- GitHub Pull Request #36346CVE reference · patch
- GitHub Pull Request #36361CVE reference · patch
- Gitea v1.25.4 ReleaseCVE reference · release-notes
- Gitea v1.25.4 Release Blog PostCVE reference · release-notes
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.