How severe is GHSA-56j7-2pm8-rgmx?

No CVSS score has been assigned to GHSA-56j7-2pm8-rgmx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-56j7-2pm8-rgmx?

GHSA-56j7-2pm8-rgmx affects the following packages: gogs.io/gogs (Go). Ecosystems affected: Go.

How do I fix GHSA-56j7-2pm8-rgmx?

Update gogs.io/gogs to 0.12.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-56j7-2pm8-rgmx is resolved across your whole dependency graph.

How do I detect GHSA-56j7-2pm8-rgmx 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-56j7-2pm8-rgmx 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.

Is GHSA-56j7-2pm8-rgmx actively exploited in the wild?

No public exploit code has been indexed for GHSA-56j7-2pm8-rgmx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-56j7-2pm8-rgmx?

GHSA-56j7-2pm8-rgmx has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 83th 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.

When was GHSA-56j7-2pm8-rgmx published, and has it been updated?

GHSA-56j7-2pm8-rgmx was published on June 2, 2022 and was last updated on July 8, 2026. 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

OS Command Injection in gogsGHSA-56j7-2pm8-rgmx

Fix: gogs/gogs#6986

GHSA-56j7-2pm8-rgmx is a security vulnerability in gogs.io/gogs. A fix is available for gogs.io/gogs — see the affected versions and patch details below.

Also known asCVE-2021-32546GO-2022-0471

Published

Jun 2, 2022

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk+0.08%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

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

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

Missing input validation in internal/db/repo_editor.go in Gogs before 0.12.8 allows an attacker to execute code remotely. An unprivileged attacker (registered user) can overwrite the Git configuration in his repository. This leads to Remote Command Execution, because that configuration can contain an option such as sshCommand, which is executed when a master branch is a remote branch (using an ssh:// URI). The remote branch can also be configured by editing the Git configuration file. One can create a new file in a new repository, using the GUI, with "" as its name, and then rename this file to .git/config with the custom configuration content (and then save it).

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

gogsgogs

< 0.12.8

range

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.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-56j7-2pm8-rgmx 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.

Frequently Asked Questions

### Impact The malicious user is able to update a crafted `config` file into repository's `.git` directory with 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 Repository file updates are prohibited to its `.git` directory. Users should upgrade to 0.12.8 or the latest 0.13.0+dev. ### Workarounds N/A ### References N/A ### For more information If you have any questions or comments about this advisory, please post on

O3 Security · Impact-Aware SCA

Is GHSA-56j7-2pm8-rgmx in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works