CVE-2026-58423

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% 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: epss, secondary
Elevated
7.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.7Exploit: NoneExposed: 0

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

LFS authentication bypass via malformed SSH sub-verb allows unauthorized read access to private repositories

CVSS v3
7.7
EG Score
7.7(medium)
EPSS
23.0%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 6, 2026

Advisory Details (4)

Auto-updated Jul 3, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_release.
github Patch Available🟡 PoC Available

LFS authentication bypass via malformed SSH sub-verb allows unauthorized read access to private repositories · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-7wvc-rvp7-w99x
github_release Patch Available

v1.26.4

Patch available: go-gitea/gitea v1.26.4

https://github.com/go-gitea/gitea/releases/tag/v1.26.4
github_pr

fix(lfs): reject unknown SSH LFS sub-verbs to prevent auth bypass

Fix merged in go-gitea/gitea PR #38008 on 2026-06-06 — awaiting tagged release

https://github.com/go-gitea/gitea/pull/38008
generic

Gitea 1.26.3 and 1.26.4 are released | Gitea Blog

https://blog.gitea.com/release-of-1.26.3-and-1.26.4/

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 49× 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-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 09:39 UTCEG score recompute
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-14 22:37 UTCEG score recompute
  7. 2026-07-14 11:38 UTCEG score recompute
  8. 2026-07-14 00:39 UTCEG score recompute
  9. 2026-07-13 22:31 UTCEPSS rescore
  10. 2026-07-13 13:40 UTCEG score recompute
  11. 2026-07-13 06:13 UTCEPSS rescore
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-13 02:41 UTCEG score recompute
  14. 2026-07-12 15:41 UTCEG score recompute
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-12 04:42 UTCEG score recompute
  17. 2026-07-11 17:42 UTCEG score recompute
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-11 08:27 UTCEPSS rescore
  20. 2026-07-11 06:42 UTCEG score recompute
  21. 2026-07-10 19:43 UTCEG score recompute
  22. 2026-07-10 08:43 UTCEG score recompute
  23. 2026-07-09 21:44 UTCEG score recompute
  24. 2026-07-09 19:10 UTCEPSS rescore
  25. 2026-07-09 19:10 UTCEPSS rescore
Show 24 more
  1. 2026-07-09 10:43 UTCEG score recompute
  2. 2026-07-08 23:41 UTCEG score recompute
  3. 2026-07-08 15:16 UTCEPSS rescore
  4. 2026-07-08 15:16 UTCEPSS rescore
  5. 2026-07-08 12:41 UTCEG score recompute
  6. 2026-07-08 01:38 UTCEG score recompute
  7. 2026-07-07 14:39 UTCEG score recompute
  8. 2026-07-07 13:46 UTCEPSS rescore
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-07 03:29 UTCEG score recompute
  11. 2026-07-06 16:29 UTCEG score recompute
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 05:29 UTCEG score recompute
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-05 18:30 UTCEG score recompute
  18. 2026-07-05 07:30 UTCEG score recompute
  19. 2026-07-05 02:31 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 20:29 UTCEG score recompute
  22. 2026-07-04 09:30 UTCEG score recompute
  23. 2026-07-03 22:30 UTCEG score recompute
  24. 2026-07-03 22:27 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58423?
CVE-2026-58423 is a high vulnerability published on July 3, 2026. LFS authentication bypass via malformed SSH sub-verb allows unauthorized read access to private repositories
When was CVE-2026-58423 disclosed?
CVE-2026-58423 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58423 actively exploited?
CVE-2026-58423 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58423?
CVE-2026-58423 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-58423?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58423, 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-58423

Explore →

Is Your Infrastructure Affected by CVE-2026-58423?

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

Start Free Scan →Browse All CVEs