fix(deps): Update dependency semantic-release to v19.0.3 [SECURITY] - #202
Merged
Merged
Conversation
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
renovate
Bot
changed the title
renovate
Bot
deleted the
renovate/npm-semantic-release-vulnerability
branch
September 17, 2026 19:16
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
September 24, 2026 03:03
162d1a3 to
fe0d006
Compare
renovate
Bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
September 24, 2026 09:30
fe0d006 to
a3defc8
Compare
3ware-release Bot
pushed a commit
that referenced
this pull request
Sep 24, 2026
## [4.21.5](v4.21.4...v4.21.5) (2026-09-24) ### Bug Fixes * **deps:** Update dependency semantic-release to v19.0.3 [SECURITY] ([#202](#202)) ([445e5d0](445e5d0))
Contributor
|
This PR is included in version 4.21.5 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
19.0.0→19.0.3Exposure of Sensitive Information to an Unauthorized Actor in semantic-release
CVE-2022-31051 / GHSA-x2pg-mjhr-2m5x
More information
Details
Impact
What kind of vulnerability is it? Who is impacted?
Secrets that would normally be masked by semantic-release can be accidentally disclosed if they contain characters that are excluded from uri encoding by encodeURI. Occurrence is further limited to execution contexts where push access to the related repository is not available without modifying the repository url to inject credentials.
Patches
Has the problem been patched? What versions should users upgrade to?
Fixed in 19.0.3
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Secrets that do not contain characters that are excluded from encoding with
encodeURIwhen included in a URL are already masked properly.References
Are there any links users can visit to find out more?
For more information
If you have any questions or comments about this advisory:
Severity
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
semantic-release/semantic-release (semantic-release)
v19.0.3Compare Source
Bug Fixes
v19.0.2Compare Source
Bug Fixes
v19.0.1Compare Source
Bug Fixes
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.