NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

Secret disclosure when containing characters that become URI encodedGHSA-r2j6-p67h-q639

HIGHFix: semantic-release/semantic-release@ca90b34

GHSA-r2j6-p67h-q639 is a high-severity (CVSS 8.1) CWE-116 vulnerability in semantic-release. A fix is available for semantic-release — see the affected versions and patch details below.

Also known asCVE-2020-26226
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk
0.00%0.63%1.27%1.90%0.2%1.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
semantic-releasenpm
4.1Mdownloads / week

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 Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmsemantic-releaseall versions17.2.3npm install semantic-release@17.2.3

Affected Products

1 product · 1 configurations
Application
semantic-releasesemantic-release_project
< 17.2.3
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for semantic-release, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update semantic-release to 17.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r2j6-p67h-q639 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact 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. ### Patches Fixed in v17.2.3 ### Workarounds Secrets that do not contain characters that become encoded when included in a URL are already masked properly.
O3 Security · Impact-Aware SCA

Is GHSA-r2j6-p67h-q639 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Secret disclosure when containing characters that…