Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.0

Kopia: Storage connection credentials written to console on "repository status" CLI command with JSON output

GHSA-j5vm-7qcc-2wwg

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/kopia/kopia 0.16.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
2.0 · CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-j5vm-7qcc-2wwg

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-j5vm-7qcc-2wwg

Advisory: Kopia: Storage connection credentials written to console on "repository status" CLI command with JSON output
IDs: GHSA-j5vm-7qcc-2wwg
Record: https://patchnext.com/advisories/ghsa-j5vm-7qcc-2wwg (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/kopia/kopia 0.16.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/kopia/kopia: affected < 0.16.0; fixed in 0.16.0

## Suggested inspection (read-only)
- Go github.com/kopia/kopia: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/kopia/kopia.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j5vm-7qcc-2wwg (GitHub-reviewed advisory GHSA-j5vm-7qcc-2wwg lists affected ranges: Go github.com/kopia/kopia >=0 <0.16.0)

Commands are suggestions: review each one before running it.

Loading voting…