CVE-2026-22555
Gitea API allows org fork without auth check.
Is CVE-2026-22555 being exploited?
Not confirmed. CVE-2026-22555 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.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-22555?
CVE-2026-22555 is rated High with a CVSS score of 8.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-22555?
Yes. A fix has been recorded for CVE-2026-22555. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-22555 affect?
CVE-2026-22555 affects Gitea <1.26.0 (self-hosted), Gitea self-hosted instances. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-22555?
Upgrade to Gitea 1.26.0+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthorized forks into an organization could expose organization secrets via forked repos.
Patch when possible
- affected< 1.26.0
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.