GHSA-j5vm-7qcc-2wwg is a low-severity (CVSS 2) vulnerability in github.com/kopia/kopia. A fix is available for github.com/kopia/kopia — see the affected versions and patch details below.
Kopia: Storage connection credentials written to console on "repository status" CLI command with JSON output
Real-World Exposure
github.com/kopia/kopiaReal-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
What kind of vulnerability is it? Who is impacted?
Storage credentials are written to the console.
Patches
Has the problem been patched? Yes, see #3589 What versions should users upgrade to?
- Any version after or including commit 1d6f852cd6534f4bea978cbdc85c583803d79f77
- No release has been created yet.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
- Be aware that
kopia repo status --jsonwill write the credentials to the output without scrubbing them. - Avoid executing
kopia repo statuswith the--jsonflag in an insecure environment where. - Avoid logging the output of the
kopia repo status --jsoncommand.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/kopia/kopia | all versions | 0.16.0go get github.com/kopia/kopia@v0.16.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kopia/kopia, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/kopia/kopia to 0.16.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j5vm-7qcc-2wwg 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-j5vm-7qcc-2wwg can be triaged on real exposure rather than presence alone.
Tailored to GHSA-j5vm-7qcc-2wwg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-j5vm-7qcc-2wwg in your dependencies?
O3 Security finds GHSA-j5vm-7qcc-2wwg across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.