How severe is GHSA-j4jw-m6xr-fv6c?

No CVSS score has been assigned to GHSA-j4jw-m6xr-fv6c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j4jw-m6xr-fv6c?

GHSA-j4jw-m6xr-fv6c affects the following packages: github.com/charmbracelet/soft-serve (Go). Ecosystems affected: Go.

How do I fix GHSA-j4jw-m6xr-fv6c?

Update github.com/charmbracelet/soft-serve to 0.8.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j4jw-m6xr-fv6c is resolved across your whole dependency graph.

How do I detect GHSA-j4jw-m6xr-fv6c in my Go dependencies?

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

How do I mitigate GHSA-j4jw-m6xr-fv6c if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-j4jw-m6xr-fv6c actively exploited in the wild?

No public exploit code has been indexed for GHSA-j4jw-m6xr-fv6c 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-j4jw-m6xr-fv6c?

GHSA-j4jw-m6xr-fv6c has an EPSS (Exploit Prediction Scoring System) score of 0.7%, 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-j4jw-m6xr-fv6c?

GHSA-j4jw-m6xr-fv6c is classified as Path Traversal (CWE-22). 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-j4jw-m6xr-fv6c published, and has it been updated?

GHSA-j4jw-m6xr-fv6c was published on January 8, 2025 and was last updated on January 8, 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

Not in CISA KEV

Soft Serve vulnerable to path traversal attacksGHSA-j4jw-m6xr-fv6c

Fix: charmbracelet/soft-serve@a8d1bf3

GHSA-j4jw-m6xr-fv6c is a Path Traversal vulnerability in github.com/charmbracelet/soft-serve. A fix is available for github.com/charmbracelet/soft-serve — see the affected versions and patch details below.

Also known asCVE-2025-22130GO-2025-3374

Published

Jan 8, 2025

Updated

Jan 8, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-j4jw-m6xr-fv6c.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐹github.com/charmbracelet/soft-serve

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

Path traversal attack gives access to existing non-admin users to access and take over other user's repositories. A malicious user then can modify, delete, and arbitrarily repositories as if they were an admin user without explicitly giving them permissions.

Patches

This is patched in v0.8.2

Workarounds

Single user set-ups are not affected. This only affects multi-user Soft Serve set-ups that enable repository creation for users. Otherwise, upgrading is necessary to circumvent the attack.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/charmbracelet/soft-serve`	all versions	0.8.2`go get github.com/charmbracelet/soft-serve@v0.8.2`

Affected Products

1 product · 1 configurations

Application

soft servecharm

< 0.8.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/charmbracelet/soft-serve, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/charmbracelet/soft-serve to 0.8.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j4jw-m6xr-fv6c is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### Impact Path traversal attack gives access to existing non-admin users to access and take over other user's repositories. A malicious user then can modify, delete, and arbitrarily repositories as if they were an admin user without explicitly giving them permissions. ### Patches This is patched in [v0.8.2](https://github.com/charmbracelet/soft-serve/releases/tag/v0.8.2) ### Workarounds Single user set-ups are not affected. This only affects multi-user Soft Serve set-ups that enable repository creation for users. Otherwise, upgrading is necessary to circumvent the attack.

O3 Security · Impact-Aware SCA

Is GHSA-j4jw-m6xr-fv6c in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works