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

Control character injection in console output in github.com/ipfs/go-ipfsGHSA-r4gv-vj59-cccm

MEDIUMFix: ipfs/go-ipfs#7831

GHSA-r4gv-vj59-cccm is a medium-severity (CVSS 6.8) CWE-116 vulnerability in github.com/ipfs/go-ipfs. A fix is available for github.com/ipfs/go-ipfs — see the affected versions and patch details below.

Also known asCVE-2020-26283GO-2022-0873
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk
0.24%0.83%1.42%2.00%0.9%1.5%May 26Aug 26Oct 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹github.com/ipfs/go-ipfs

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

Control characters are not escaped from console output. This can result in hiding input from the user which could result in the user taking an unknown, malicious action.

Patches

<!-- _Has the problem been patched? What versions should users upgrade to?_ -->

For more information

If you have any questions or comments about this advisory:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/ipfs/go-ipfsall versions0.8.0go get github.com/ipfs/go-ipfs@v0.8.0

Affected Products

1 product · 1 configurations
Application
go-ipfsprotocol
< 0.8.0
range

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/ipfs/go-ipfs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/ipfs/go-ipfs to 0.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r4gv-vj59-cccm 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 Control characters are not escaped from console output. This can result in hiding input from the user which could result in the user taking an unknown, malicious action. ### Patches <!-- _Has the problem been patched? What versions should users upgrade to?_ --> - Patched via https://github.com/ipfs/go-ipfs/pull/7831 in v0.8.0 ### For more information If you have any questions or comments about this advisory: * Open an issue in [go-ipfs](http://github.com/ipfs/go-ipfs) * Email us at [[email protected]](mailto:[email protected])
O3 Security · Impact-Aware SCA

Is GHSA-r4gv-vj59-cccm in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Control character injection in console output in…