NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
LOW severity

Kopia: Storage connection credentials written to console on "repository status" CLI command with JSON outputGHSA-j5vm-7qcc-2wwg

LOWFix: kopia/kopia#3589

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.

Also known asGO-2024-2703
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/kopia/kopia

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

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 --json will write the credentials to the output without scrubbing them.
  • Avoid executing kopia repo status with the --json flag in an insecure environment where.
  • Avoid logging the output of the kopia repo status --json command.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/kopia/kopiaall versions0.16.0go get github.com/kopia/kopia@v0.16.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. 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.

  3. 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 _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 --json` will write the credentials to the output without scrubbing them. - Avoid executing `kopia repo status` with the `--json` fl
O3 Security · Impact-Aware SCA

Is GHSA-j5vm-7qcc-2wwg in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Kopia: Storage connection credentials written to console…