LiveActive security incident?Get immediate response
CVE Record

CVE-2020-26283: Control character injection in console output

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.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Older go-ipfs releases can print unescaped control characters to a terminal. A maliciously crafted output could visually hide or alter what an operator sees, increasing the chance they approve or type an unintended action. The issue is fixed in go-ipfs 0.8.0.

Executive priority

Treat as a moderate operational integrity issue. Prioritize remediation where go-ipfs is used by administrators or automated support teams, because the business risk is misleading console output that can cause human error during sensitive operations.

Technical view

CVE-2020-26283 affects go-ipfs versions before 0.8.0. The flaw is improper output neutralization for console control characters, mapped to CWE-116. CVSS 3.1 is 6.8 with low attack complexity, required privileges, required user interaction, changed scope, and high integrity impact.

Likely exposure

Exposure is most likely where go-ipfs before 0.8.0 is installed and operators rely on terminal output during interactive or administrative workflows. Server-side risk depends on whether vulnerable console output is visible to a user who can be influenced into an action.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The CVSS vector indicates exploitation requires some privileges and user interaction. The described impact is terminal deception leading to unknown malicious action, not direct confidentiality loss or service outage.

Researcher notes

Evidence is limited to the CVE description, GitHub advisory, PR, and commit. Do not claim broader IPFS implementation impact. Focus validation on go-ipfs versioning and console-output handling before 0.8.0.

Mitigation direction

  • Upgrade go-ipfs to version 0.8.0 or later.
  • Inventory endpoints, servers, containers, and build images for go-ipfs versions before 0.8.0.
  • Review the GitHub advisory and fixing commit for vendor-specific remediation details.
  • Limit interactive use of vulnerable go-ipfs consoles until upgraded.

Validation and detection

  • Check installed go-ipfs versions and flag anything below 0.8.0.
  • Confirm package, container, and deployment manifests reference go-ipfs 0.8.0 or later.
  • Verify operational runbooks no longer depend on vulnerable versions.
  • Record advisory, PR, and commit evidence in the vulnerability ticket.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-116: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-26283 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N2.34Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.8Medium
CVSS 3.1 vector shape for CVE-2020-26283Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ipfsgo-ipfs< 0.8.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-116 · source CWE mapping

Improper Encoding or Escaping of Output

Improper Encoding or Escaping of Output represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.