How severe is GHSA-3h6c-c475-jm7v?

GHSA-3h6c-c475-jm7v has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-3h6c-c475-jm7v?

GHSA-3h6c-c475-jm7v affects the following packages: code.gitea.io/gitea (Go). Ecosystems affected: Go.

How do I fix GHSA-3h6c-c475-jm7v?

Update code.gitea.io/gitea to 1.12.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3h6c-c475-jm7v is resolved across your whole dependency graph.

How do I detect GHSA-3h6c-c475-jm7v in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for code.gitea.io/gitea. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-3h6c-c475-jm7v if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-3h6c-c475-jm7v?

O3 pinpoints whether GHSA-3h6c-c475-jm7v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-3h6c-c475-jm7v actively exploited in the wild?

Yes. There are 6 known exploit references for GHSA-3h6c-c475-jm7v, including 5 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-3h6c-c475-jm7v?

GHSA-3h6c-c475-jm7v has an EPSS (Exploit Prediction Scoring System) score of 95.4%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-3h6c-c475-jm7v?

GHSA-3h6c-c475-jm7v is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-3h6c-c475-jm7v?

A Nuclei detection template exists for GHSA-3h6c-c475-jm7v, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-3h6c-c475-jm7v published, and has it been updated?

GHSA-3h6c-c475-jm7v was published on April 22, 2024 and was last updated on April 22, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-3h6c-c475-jm7v

HIGH

Arbitrary Code Execution in Gitea

Also known asBIT-gitea-2020-14144CVE-2020-14144

Published

Apr 22, 2024

Updated

Apr 22, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

6 known

EPSS Exploitation Probability

via FIRST.org ↗

95.4%probability of exploitation in next 30 days

Very High Risk100th percentile+1.74%

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.

Blast Radius

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

The git hook feature in Gitea 1.1.0 through 1.12.5 allows for authenticated remote code execution.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`code.gitea.io/gitea`	≥ 1.1.0&&< 1.12.6	1.12.6

Exploits & PoCs

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