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

> Attackers can view sensitive secrets in logs if they contain URL-encoded characters, affecting users of the semantic-release npm package.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r2j6-p67h-q639

## What is CVE-2020-26226?

CVE-2020-26226 is a high-severity vulnerability in semantic-release, published on 18 Nov 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

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

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2020-26226?

2 open source packages ship an affected version, including semantic-release. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `semantic-release` | npm | All versions | 17.2.3 |
| `semantic-release` | npm | All versions | 17.2.3 |

Products: Semantic-Release Project Semantic-Release.

## How do I fix CVE-2020-26226?

Upgrade semantic-release to 17.2.3 or later.

## Is CVE-2020-26226 being exploited?

There is no known exploitation of CVE-2020-26226 in the wild and no public exploit code.

## Other vulnerabilities in semantic-release

- [CVE-2022-31051](https://insights.sbomify.com/CVE-2022-31051/): Exposure of Sensitive Information to an Unauthorized Actor in semantic-release (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26226 and fix it if it is affected.

What it is: CVE-2020-26226 is a high-severity vulnerability in semantic-release, published on 18 Nov 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-26226 in the wild and no public exploit code.

Affected packages and fixed versions:
- semantic-release (npm): affected all versions; fixed in 17.2.3
- semantic-release (npm): affected all versions; fixed in 17.2.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-26226/ (Markdown: https://insights.sbomify.com/CVE-2020-26226/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-26226
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-26226
- OSV: https://osv.dev/vulnerability/CVE-2020-26226

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-26226/
Summaries are generated and may contain mistakes; the official description above is the record.