GHSA-644v-xv3j-xgqg — gitea
Fix: go-gitea/gitea#36340GHSA-644v-xv3j-xgqg is a CWE-284 vulnerability in gitea. A fix is available for gitea — see the affected versions and patch details below.
Gitea Stopwatch API Missing Authorization Check Leads to Post-Revocation Information Disclosure
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-644v-xv3j-xgqg.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
giteaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.
Description
Gitea's stopwatch API does not re-validate repository access permissions. After a user's access to a private repository is revoked, they may still view issue titles and repository names through previously started stopwatches.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦Bitnami | gitea | all versions | 1.25.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gitea, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update gitea to 1.25.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-644v-xv3j-xgqg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-644v-xv3j-xgqg can be triaged on real exposure rather than presence alone.
Tailored to GHSA-644v-xv3j-xgqg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for GHSA-644v-xv3j-xgqg (CC BY 4.0)
Frequently Asked Questions
Is GHSA-644v-xv3j-xgqg in your dependencies?
O3 Security finds GHSA-644v-xv3j-xgqg across Bitnami dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.