Kopia: Storage connection credentials written to console on "repository status" CLI command with JSON output
Summary
GHSA-j5vm-7qcc-2wwg: Impact _What kind of vulnerability is it? Affects github.com/kopia/kopia versions < 0.16.0. Fixed in 0.16.0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Kopia is an open-source backup tool written in Go. It provides a command-line interface (CLI) for managing backups and repositories. The tool allows users to store their backups in various storage providers, such as local filesystems, S3, and Google Cloud Storage. Kopia supports JSON output for CLI commands, including the "repository status" command.
Vulnerability Detail
The vulnerability in Kopia allows storage connection credentials to be written to the console when executing the "repository status" CLI command with JSON output. This means that sensitive information, such as access keys or passwords, can be unintentionally exposed to anyone with access to the console output. The impact of this vulnerability is low, as it requires the user to explicitly request JSON output and log or display the output in an insecure environment.
How To Fix
Latest published version: v0.23.1 as of 23 Oct 2026
go get github.com/kopia/kopia@v0.23.1Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
0.16.0
This is the first release that contains the fix.
go get github.com/kopia/kopia@v0.16.0Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
If upgrading to the patched version is not immediately possible, users can take the following workaround:
- Avoid executing the "kopia repo status" command with the "--json" flag in an insecure environment.
- Be aware that executing "kopia repo status --json" will write the storage connection credentials to the console output without scrubbing them.
- Avoid logging or displaying the output of the "kopia repo status --json" command in an insecure environment.
Conclusion
The vulnerability in Kopia that exposes storage connection credentials in the console output has been addressed with a patch. Users should upgrade to the latest version of the Kopia package that includes the fix. If immediate upgrade is not possible, follow the provided workaround to mitigate the risk. For further support on vulnerability remediation, contact DevNack.com.
See every vulnerability recorded for github.com/kopia/kopia →
FAQ
The impact of this vulnerability is low. It requires the user to explicitly request JSON output and log or display the output in an insecure environment. If proper precautions are taken, the exposure of storage connection credentials can be mitigated.
To fix this vulnerability, upgrade to the latest version of the Kopia package that includes the patch. Follow the provided steps in the "how_to_fix" section for detailed instructions.
Yes, you can continue using Kopia without JSON output. This vulnerability only affects the "repository status" command when executed with the "--json" flag.
Yes, there are several alternative backup tools available in the market. Some popular options include Duplicacy, Restic, and BorgBackup. Evaluate these tools based on your specific requirements and choose the one that best suits your needs.
You can find more information about Kopia on the official project website (https://kopia.io) and the GitHub repository (https://github.com/kopia/kopia). The documentation provides detailed usage instructions, configuration options, and examples.
References
Related vulnerabilities
Recent vulnerabilities recorded for github.com/kopia/kopia.
