CVE-2026-58510
CVE-2026-58510 — GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->private
GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->private
Published Updated Sources: NVD, Gitea (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Exploit code
public exploit, none observed
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
Unscored
no source published a base score
Remediation
The vendor's own words where we have them.
Upgrade code.gitea.io/gitea to 1.27.0 or later (go advisory GHSA-q423-49rw-g9mh).
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| Gitea | Gitea Open Source Git Server | 0 to <= 1.26.4 | Vulnerable |
| go | code.gitea.io/gitea | < 1.27.0 | Vulnerable |
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 4.3 | CVSS 3.1 | medium | — | — | GHSA |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-281 · Improper Preservation of Permissions
- Read Application Data
- Modify Application Data::
CWE-359 · Exposure of Private Personal Information to an Unauthorized Actor
- Read Application Data::
Mitigation: Identify and consult all relevant regulations for personal privacy. An organization may be required to comply with certain federal and state regulations, depending on its location, the type of business it conducts, and the nature of any private data it handles. Regulations may include Safe Harbor Privacy Framework [REF-340], Gramm-Leach Bliley Act (GLBA) [REF-341], Health Insurance Portability and Accountability Act (HIPAA) [REF-342], General Data Protection Regulation (GDPR) [REF-1047], California Consumer Privacy Act (CCPA) [REF-1048], and others.
Weakness & attack patterns
- CWE-200
- CWE-281
- CWE-359
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1562.003Impair Defenses: Impair Command History Logging
- T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
- T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
1
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Initial · CVE published
Aug 13, 2026 · NVD
Added · GHSA-q423-49rw-g9mh published (medium)
Jul 21, 2026 · GitHub Security Advisory
Source activity
Readings a source repeats on a schedule, counted rather than listed.
- 1×CVE modified by NIST, Modified, LinkAug 13, 2026 · SOCRadar CTI
References
4 on the record
- blog.gitea.com/gitea-1.27.0-is-released/
Vendor Advisory
- github.com/go-gitea/gitea/releases/tag/v1.27.0
Exploit, Third Party Advisory, Mitre, NIST
- github.com/go-gitea/gitea/security/advisories/GHSA-q423-49rw-g9mh
Exploit, Third Party Advisory, Mitre, NIST
- github.com/advisories/GHSA-q423-49rw-g9mh
Exploit, Third Party Advisory
Elsewhere on this site
- Giteaevery CVE for this vendor
- goevery CVE for this vendor
- Remote Code Execsame class
- CWE-200other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-58510 is GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->private, a unscored vulnerability affecting Gitea Open Source Git Server, code.gitea.io/gitea from Gitea, go. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-58510. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS null describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.