Security readout for executives and security teams
Plain-English summary
A Gitea authorization flaw can bypass an organization policy governing who may link teams to repositories. If a deployment is affected, unauthorized repository access changes could expose source code or permit unwanted modification. The supplied version data is insufficient to identify affected installations reliably.
Executive priority
Treat this as an urgent exposure-validation task because successful abuse could compromise proprietary source code and repository integrity. Prioritize internet-accessible or broadly accessible Gitea instances. Do not declare compromise solely from the critical score; confirm versions, configuration, and suspicious access changes. Active exploitation is not established by the supplied evidence.
Technical view
CVE-2026-58433 is a CWE-862 missing-authorization issue in the team-repository linking endpoint. It bypasses the RepoAdminChangeTeamAccess organization setting. CVSS 3.1 rates it 9.1: network-accessible, low complexity, no privileges or user interaction, with high confidentiality and integrity impact but no stated availability impact.
Likely exposure
Potential exposure centers on Gitea deployments using organization teams and relying on RepoAdminChangeTeamAccess to prevent unauthorized access changes. The bundle lists version “0” with a default unaffected status, which does not establish a usable affected-version range. Confirm applicability through the vendor advisory before classifying any deployment as vulnerable.
Exploitation context
The supplied record is not in CISA KEV, and no cited source in the bundle states that active exploitation has occurred. The CVSS vector indicates a remotely reachable, low-complexity condition requiring no privileges, but that score alone is not evidence of exploitation or public weaponization.
Researcher notes
The central security boundary is authorization enforcement on team-repository linking, specifically consistency with RepoAdminChangeTeamAccess. The supplied affected entry—version “0” and default unaffected—is ambiguous and cannot support precise version matching. The references include Gitea 1.27.0 materials, but the bundle does not explicitly establish that release as the fix.
Mitigation direction
- Check the vendor advisory for the authoritative affected-version range and remediation guidance.
- Upgrade to a vendor-confirmed fixed release when applicability is established.
- Restrict Gitea access to trusted networks while exposure remains unresolved.
- Audit and correct unexpected team-to-repository links and resulting permissions.
- Preserve relevant access and administration logs for investigation.
Validation and detection
- Inventory every deployed Gitea version and organization using team-based repository access.
- Compare installed versions against the current vendor advisory.
- Review team-repository links for additions inconsistent with approved access records.
- Confirm RepoAdminChangeTeamAccess is configured as intended for each organization.
- After remediation, verify unauthorized users cannot change team-repository associations.
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-862: 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-58433 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
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
SSVC decision data
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:N/UI:N/S:U/C:H/I:H/A:N3.95.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security AdvisoryCVE reference, Gitea · vendor-advisory
- Gitea v1.27.0 ReleaseCVE reference, Gitea · release-notes
- Gitea v1.27.0 Release Blog PostCVE reference, Gitea · 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.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.