Skip to content
major vulnerability· requires attention

Bypasses org-level repo access control, enabling unauthorized team-repo linking across widely used code-hosting platforms; high-impact for software supply and IP protection.

Applications

CVE-2026-58433

9.1
Critical
EPSS 0.28%Patch availableAug 15, 2026

Auth bypass lets teams be linked to repos despite org deny setting.

common questions

Is CVE-2026-58433 being exploited?

Not confirmed. CVE-2026-58433 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.

How severe is CVE-2026-58433?

CVE-2026-58433 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-58433?

Yes. A fix has been recorded for CVE-2026-58433. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-58433 affect?

CVE-2026-58433 affects Platforms implementing 'RepoAdminChangeTeamAccess' org setting (code-hosting services). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-58433?

Restrict/admin audit team-linking, monitor repository access, apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Platforms implementing 'RepoAdminChangeTeamAccess' org setting (code-hosting services)
impact

Attackers can link teams to repositories despite RepoAdminChangeTeamAccess, granting unauthorized repo access, data exposure, and potential code tampering.

action required

Immediate action required

affected versions
Gitea Gitea Open Source Git Server
  • affected<= 1.26.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free