CVE-2020-26226

Secret disclosure in semantic-release

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.

Category

8.1
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.39%
Third-Party Advisory github.com Third-Party Advisory github.com
Affected: semantic-release semantic-release
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2020-26226?
CVE-2020-26226 has been scored as a high severity vulnerability.
How to fix CVE-2020-26226?
To fix CVE-2020-26226, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-26226 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-26226 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-26226?
CVE-2020-26226 affects semantic-release semantic-release.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.