CVE-2026-22555

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

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

Gitea versions before 1.26.0 allow API users to fork a repository into an organization without first passing the CanCreateOrgRepo check, which can expose organization secrets.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
22.2%
KEV
Not listed

Published

June 17, 2026

Last Modified

July 6, 2026

Advisory Details (4)

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

API Fork Missing CanCreateOrgRepo Check Allows Org Secret Exfiltration · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-fhx7-m96w-mv29
github_release Patch Available

v1.26.0

Patch available: go-gitea/gitea v1.26.0

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

Fix a bug when forking a repository in an organization

Fix merged in go-gitea/gitea PR #36950 on 2026-04-02 — awaiting tagged release

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

Gitea 1.26.0 is released | Gitea Blog

https://blog.gitea.com/release-of-1.26.0/

Vendor Advisories for CVE-2026-22555(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
code.gitea.io/gitea1.26.0

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 44× 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-07 05:29 UTCEG score recompute
  2. 2026-07-06 17:08 UTCEG score recompute
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 04:57 UTCEG score recompute
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-05 16:33 UTCEG score recompute
  9. 2026-07-05 04:23 UTCEG score recompute
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 15:41 UTCEG score recompute
  12. 2026-07-04 03:28 UTCEG score recompute
  13. 2026-07-03 14:01 UTCEG score recompute
  14. 2026-07-03 01:49 UTCEG score recompute
  15. 2026-07-02 13:39 UTCEG score recompute
  16. 2026-07-02 01:29 UTCEG score recompute
  17. 2026-07-01 13:18 UTCEG score recompute
  18. 2026-07-01 01:04 UTCEG score recompute
  19. 2026-06-30 12:53 UTCEG score recompute
  20. 2026-06-30 00:43 UTCEG score recompute
  21. 2026-06-29 12:33 UTCEG score recompute
  22. 2026-06-29 00:23 UTCEG score recompute
  23. 2026-06-28 12:12 UTCEG score recompute
  24. 2026-06-28 00:00 UTCEG score recompute
  25. 2026-06-27 11:50 UTCEG score recompute
Show 19 more
  1. 2026-06-26 23:39 UTCEG score recompute
  2. 2026-06-26 11:29 UTCEG score recompute
  3. 2026-06-25 21:53 UTCEG score recompute
  4. 2026-06-25 09:42 UTCEG score recompute
  5. 2026-06-24 21:32 UTCEG score recompute
  6. 2026-06-24 09:21 UTCEG score recompute
  7. 2026-06-23 21:10 UTCEG score recompute
  8. 2026-06-23 08:56 UTCEG score recompute
  9. 2026-06-22 20:45 UTCEG score recompute
  10. 2026-06-22 08:35 UTCEG score recompute
  11. 2026-06-21 20:24 UTCEG score recompute
  12. 2026-06-21 08:12 UTCEG score recompute
  13. 2026-06-20 19:58 UTCEG score recompute
  14. 2026-06-20 07:46 UTCEG score recompute
  15. 2026-06-19 19:34 UTCEG score recompute
  16. 2026-06-19 07:22 UTCEG score recompute
  17. 2026-06-18 19:10 UTCEG score recompute
  18. 2026-06-18 06:58 UTCEG score recompute
  19. 2026-06-17 18:46 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-22555?
CVE-2026-22555 is a high vulnerability published on June 17, 2026. Gitea versions before 1.26.0 allow API users to fork a repository into an organization without first passing the CanCreateOrgRepo check, which can expose organization secrets.
When was CVE-2026-22555 disclosed?
CVE-2026-22555 was first published in the National Vulnerability Database on June 17, 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-22555 actively exploited?
CVE-2026-22555 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-22555?
CVE-2026-22555 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-22555?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-22555, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-22555

Explore →

Is Your Infrastructure Affected by CVE-2026-22555?

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