Security readout for executives and security teams
Plain-English summary
CVE-2026-0798 is a low-severity information leak in Gitea release email notifications. People who previously watched a repository may continue receiving release emails after their access is revoked or after the repository becomes private. Those emails can expose private release titles, tags, and content.
Executive priority
Handle during normal patch governance unless private release notes contain sensitive data. Prioritize faster if Gitea hosts confidential product plans, customer-specific releases, or security-related release content.
Technical view
The issue is an access-control failure in Gitea notification handling for private repository releases. The CVSS is 3.5, with network exposure, low attack complexity, low confidentiality impact, and no integrity or availability impact. The provided data links a fix to Gitea pull request #36319 and release v1.25.4, but does not provide a clear affected version range.
Likely exposure
Exposure is most likely for Gitea instances using release email notifications on repositories that changed from public to private or had watcher access revoked. Risk is highest where release notes contain sensitive roadmap, customer, security, or deployment details.
Exploitation context
No active exploitation is indicated in the provided sources, and the CVE is not listed as KEV. The issue does not require code execution; it is an unintended disclosure through normal email notification flows to previously authorized watchers.
Researcher notes
The source bundle identifies CWE-284 and a patch reference, but the affected version range is unclear. Validate against the GitHub advisory, PR #36319, and v1.25.4 notes before making fleet-wide assumptions. Do not treat this as active exploitation without new evidence.
Mitigation direction
- Review the Gitea advisory and v1.25.4 release notes for vendor guidance.
- Upgrade to a fixed Gitea release if your deployed version is affected.
- Audit private repository watchers and notification recipients after access changes.
- Avoid placing sensitive details in release notes until remediation is confirmed.
Validation and detection
- Identify Gitea instances with release email notifications enabled.
- Check whether repositories were made private after being public.
- Review recent release email recipients for revoked or unauthorized users.
- Confirm deployed Gitea version against vendor 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 lookupCVE-2026-0798 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
- Low
- CVSS
- 3.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/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:R/S:U/C:L/I:N/A:N2.11.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.5LowVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security AdvisoryCVE reference · vendor-advisory
- GitHub Pull Request #36319CVE 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.