NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

CVE-2022-30781 — gitea

HIGHFix: go-gitea/gitea#19487

CVE-2022-30781 is a high-severity (CVSS 7.5) CWE-116 vulnerability in code.gitea.io/gitea. 6 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for code.gitea.io/gitea — see the affected versions and patch details below.

Shell command injection in gitea

Also known asBIT-gitea-2022-30781GHSA-p5f9-c9j9-g8qxGO-2022-0450
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
6 known
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
87.9%probability of exploitation in next 30 days
Very High Risk0.00%
Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk
78.1%82.7%87.3%92.0%80.7%87.9%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

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 before 1.16.7 does not escape the shell out for git fetch remote allowing for shell command injection

Affected Packages

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

Affected Products

1 product · 1 configurations
Application
giteagitea
< 1.16.7
range
Exploits & PoCs
6

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

EDB-51009webappsmultiple✓ Verified

Gitea 1.16.6 - Remote Code Execution (RCE) (Metasploit)

by samguy · Sep 15, 2022

Exploit-DB Source

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.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-30781 is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

Gitea before 1.16.7 does not escape the shell out for `git fetch remote` allowing for shell command injection
O3 Security · Impact-Aware SCA

Is CVE-2022-30781 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-30781: gitea — Fixed in 1.16.7