CVE-2026-58433

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization setting

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Attend)
EG Risk 72/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 26, 2026

Advisory Details (1)

Auto-updated Aug 29, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization setting · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-m6qc-j894-7h9r

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 04:07 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 07:36 UTCEG score recompute
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-26 16:27 UTCEG score recompute
  6. 2026-08-26 14:46 UTCEPSS rescore
  7. 2026-08-25 17:13 UTCEG score recompute
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-24 18:02 UTCEG score recompute
  10. 2026-08-24 10:25 UTCEG score recompute
  11. 2026-08-23 03:54 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 01:17 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 02:20 UTCEG score recompute
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-19 19:50 UTCEG score recompute
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-18 17:06 UTCEG score recompute
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 16:50 UTCEG score recompute
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-16 17:56 UTCEG score recompute
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 02:43 UTCEG score recompute
Show 9 more
  1. 2026-08-16 02:14 UTCEPSS rescore
  2. 2026-08-15 03:55 UTCEG score recompute
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-15 00:06 UTCEG score recompute
  5. 2026-08-14 19:39 UTCEG score recompute▲ 9.10
  6. 2026-08-14 19:38 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  7. 2026-08-13 17:17 UTCNVD update
  8. 2026-08-13 17:02 UTCEG score recompute
  9. 2026-08-13 17:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-58433?
CVE-2026-58433 is a critical vulnerability published on August 13, 2026. Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization setting
When was CVE-2026-58433 disclosed?
CVE-2026-58433 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58433 actively exploited?
CVE-2026-58433 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.5% of all scored CVEs.
What is the CVSS score of CVE-2026-58433?
CVE-2026-58433 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-58433?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58433, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-58433

Explore →

Is Your Infrastructure Affected by CVE-2026-58433?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs