CVE-2020-26226

Secret disclosure in semantic-release

HIGH
8.1
CVSS Score
Published: November 18, 2020 at 09:35 PM UTC
Updated: June 17, 2026 at 03:07 AM UTC
2 products affected across 2 vendorsSemantic ReleaseRelease Project Semantic Release

Using semantic-release by semantic-release?

Get instant alerts when new vulnerabilities affect semantic-release - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.1
Exploit prediction
EPSS 1%

Description

In the npm package semantic-release before version 17.2.3, secrets that would normally be masked by `semantic-release` can be accidentally disclosed if they contain characters that become encoded when included in a URL. Secrets that do not contain characters that become encoded when included in a URL are already masked properly. The issue is fixed in version 17.2.3.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 17.2.3
Affected range stops below 17.2.3, so it looks safe — our inference, not a vendor statement
v < 6.1.5
Affected range stops below 6.1.5, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

8.1HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-116

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card