Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

Gitea Missing Authorization vulnerabilityGHSA-jr9c-h74f-2v28

HIGHFix: go-gitea/gitea@1314f38

GHSA-jr9c-h74f-2v28 is a high-severity (CVSS 7.1) CWE-862 vulnerability in code.gitea.io/gitea. 1 public exploit reference exists, so weaponization risk is real. A fix is available for code.gitea.io/gitea — see the affected versions and patch details below.

Also known asBIT-gitea-2022-0905CVE-2022-0905GO-2022-0609
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk
0.00%0.45%0.90%1.35%0.3%0.8%May 26Sep 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-jr9c-h74f-2v28 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
🐹code.gitea.io/gitea

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Gitea 1.16.3 and prior is vulnerable to missing authorization. A patch is available as part of the 1.16.4 release.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gocode.gitea.io/giteaall versions1.16.4go get code.gitea.io/gitea@v1.16.4

Affected Products

1 product · 1 configurations
Application
giteagitea
< 1.16.4
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.…

huntr.devNVDMar 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for code.gitea.io/gitea, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update code.gitea.io/gitea to 1.16.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jr9c-h74f-2v28 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Gitea 1.16.3 and prior is vulnerable to missing authorization. A patch is available as part of the 1.16.4 release.
O3 Security · Impact-Aware SCA

Is GHSA-jr9c-h74f-2v28 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Gitea Missing Authorization vulnerability (High 7.1)