CVE-2020-26226: In the npm package semantic-release before version 17.2.3, secrets that would normally be masked by `semantic-

Q: How do I fix CVE-2020-26226?

semantic-release: upgrade to 17.2.3. Exact commands for each OS are on this page.

Q: Is CVE-2020-26226 being exploited?

CVE-2020-26226 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-26226 affect?

CVE-2020-26226 affects semantic-release. Severity is high (CVSS 8.1). 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

This month

HIGH 8.1UPGRADE

CVE-2020-26226 is a high-severity flaw (CVSS 8.1) affecting semantic-release. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.4% (top 28%)
CISA exploited list	No
Weakness	CWE-116
Published	2020-11-18
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: semantic-release project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-11-18 22:15 UTCPublished CVE record published
2026-06-17 03:07 UTCUpdated Record last modified

semantic-release project semantic-release UPGRADE

Affected: < 17.2.3

Fixed in: 17.2.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy semantic-release || rpm -q semantic-release || semantic-release --version

2. UPGRADE to 17.2.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade semantic-release

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade semantic-release

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-26226?

semantic-release: upgrade to 17.2.3. Exact commands for each OS are on this page.

Is CVE-2020-26226 being exploited?

CVE-2020-26226 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-26226 affect?

CVE-2020-26226 affects semantic-release. Severity is high (CVSS 8.1). 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

How urgent is CVE-2020-26226?

Priority 46/100. High severity

Software pages

npm packages vulnerabilities

Related CVEs

CVE-2022-31051 MEDIUM 4.4 UPGRADE semantic-release is an open source npm package for automated version management and package publishing

References

← Back to latest CVEs