Skip to content
Fencer Intel
medium 6.8

CVE-2020-26283 json

Control character injection in console output

published 5y ago modified last mo. also GHSA-r4gv-vj59-cccm , GO-2022-0873 , EUVD-2021-1391

cvss
6.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

Summary

go-ipfs is an open-source golang implementation of IPFS which is a global, versioned, peer-to-peer filesystem. In go-ipfs before version 0.8.0, 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. This is fixed in version 0.8.0.

Patch / fix

  • go github.com/ipfs/go-ipfs 0.8.0
  • protocol go-ipfs 0.8.0
  • kubo Alpine 3.24, Alpine 3.23, Alpine 3.22 +5 more 0.8.0-r0
  • go-ipfs Alpine 3.16, Alpine 3.15, Alpine 3.14 +1 more 0.8.0-r0

alpine advisories ALPINE-CVE-2020-26283

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2020-26283 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.50% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub 3.1 6.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/ipfs/go-ipfs
<0.8.0
0.8.0

Affected products

  • ipfs go-ipfs

Classification

Weakness
  • CWE-116 Improper Encoding or Escaping of Output
  • CWE-150 Improper Neutralization of Escape, Meta, or Control Sequences

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.