How severe is GHSA-67mx-jc2f-jgjm?

GHSA-67mx-jc2f-jgjm has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-67mx-jc2f-jgjm?

GHSA-67mx-jc2f-jgjm affects the following packages: gogs.io/gogs (Go). Ecosystems affected: Go.

How do I fix GHSA-67mx-jc2f-jgjm?

Update gogs.io/gogs to 0.12.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-67mx-jc2f-jgjm is resolved across your whole dependency graph.

How do I detect GHSA-67mx-jc2f-jgjm in my Go dependencies?

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

How do I mitigate GHSA-67mx-jc2f-jgjm if there is no patch (or I can't update yet)?

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.

Is GHSA-67mx-jc2f-jgjm actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-67mx-jc2f-jgjm, including 1 in-the-wild exploitation 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-67mx-jc2f-jgjm?

GHSA-67mx-jc2f-jgjm has an EPSS (Exploit Prediction Scoring System) score of 4.2%, placing it in the 91th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-67mx-jc2f-jgjm?

GHSA-67mx-jc2f-jgjm 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.

When was GHSA-67mx-jc2f-jgjm published, and has it been updated?

GHSA-67mx-jc2f-jgjm was published on June 8, 2022 and was last updated on August 21, 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

Not in CISA KEV

CRITICAL severity

OS Command Injection in file editor in GogsGHSA-67mx-jc2f-jgjm

CRITICALFix: gogs/gogs@38aff73

GHSA-67mx-jc2f-jgjm is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in gogs.io/gogs. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for gogs.io/gogs — see the affected versions and patch details below.

Also known asCVE-2022-1986GO-2022-0556

Published

Jun 8, 2022

Updated

Aug 21, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

4.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

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

🐹gogs.io/gogs

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

Impact

The malicious user is able to update a crafted config file into repository's .git directory in combination with crafted file deletion to gain SSH access to the server. All installations with repository upload enabled (default) are affected.

Patches

File deletions are prohibited to repository's .git directory. Users should upgrade to 0.12.9 or the latest 0.13.0+dev.

Workarounds

N/A

References

https://huntr.dev/bounties/776e8f29-ff5e-4501-bb9f-0bd335007930/

For more information

If you have any questions or comments about this advisory, please post on #7000.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`gogs.io/gogs`	all versions	0.12.9`go get gogs.io/gogs@v0.12.9`

Affected Products

1 product · 1 configurations

Application

gogsgogs

< 0.12.9

range

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.

OS Command Injection in GitHub repository gogs/gogs prior to 0.12.9.

huntr.devNVDJun 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gogs.io/gogs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update gogs.io/gogs to 0.12.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-67mx-jc2f-jgjm is resolved across your whole dependency graph.
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

### Impact The malicious user is able to update a crafted `config` file into repository's `.git` directory in combination with crafted file deletion to gain SSH access to the server. All installations with [repository upload enabled (default)](https://github.com/gogs/gogs/blob/f36eeedbf89328ee70cc3a2e239f6314f9021f58/conf/app.ini#L127-L129) are affected. ### Patches File deletions are prohibited to repository's `.git` directory. Users should upgrade to 0.12.9 or the latest 0.13.0+dev. ### Workarounds N/A ### References https://huntr.dev/bounties/776e8f29-ff5e-4501-bb9f-0bd335007930/ ##

O3 Security · Impact-Aware SCA

Is GHSA-67mx-jc2f-jgjm in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-78OS Command Injection

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Jun 8, 2022

First exploit

Jun 15, 2022

7 days after disclosure — rapid exploitation

Last updated

Aug 21, 2024

Identifiers

GHSA-67mx-jc2f-jgjm

GO-2022-0556

References

Advisorynvd.nist.gov · CVE 2022 1986 Webgithub.com · GHSA 67mx jc2f jgjm Webgithub.com · 38aff73251cc46ced96dd608dab6190415032a82 Webgithub.com · app.ini Webhuntr.dev · 776e8f29 ff5e 4501 bb9f 0bd335007930 Packagegithub.com · gogs

Related vulnerabilities

This CVE is critical severity; 2 of 8 other CVEs affecting gogs are rated as high or higher (top: critical).

CVE-2026-52808CVE-2026-52816CVE-2026-52804CVE-2026-52809CVE-2026-52812CVE-2026-52815CVE-2026-52811CVE-2026-52813

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 21, 2024