Security readout for executives and security teams
Plain-English summary
semantic-release could accidentally reveal repository or publishing secrets in logs when credentials are embedded in repository URLs and contain certain characters. The issue is narrow because it requires high privileges and a specific release workflow, but leaked tokens can still create serious follow-on risk.
Executive priority
Treat as a targeted CI/CD hygiene issue. Prioritize teams publishing packages with semantic-release, especially where release tokens have broad repository or registry permissions.
Technical view
Affected semantic-release versions >=17.0.4 and <19.0.3 could fail to mask secrets containing characters not encoded by JavaScript encodeURI. The advisory limits exposure to contexts where push access is unavailable unless the repository URL is modified to inject credentials.
Likely exposure
Most likely exposure is CI/CD release jobs using semantic-release with credentials injected into repository URLs. Organizations not using affected versions, or not embedding secrets this way, are unlikely to be affected.
Exploitation context
The bundle does not cite active exploitation, and KEV is false. Abuse would require privileged ability to influence or observe release execution where affected secret masking fails, making opportunistic exploitation less likely.
Researcher notes
Evidence supports a constrained information disclosure issue, not remote code execution. The critical research question is whether affected workflows inject credentials into repository URLs and whether logs are accessible beyond trusted maintainers.
Mitigation direction
- Upgrade semantic-release to version 19.0.3 or later.
- Follow the GitHub advisory workaround if immediate upgrade is not possible.
- Check CI logs for exposed release tokens or repository credentials.
- Rotate any credentials confirmed exposed in logs or artifacts.
Validation and detection
- Inventory projects using semantic-release versions >=17.0.4 and <19.0.3.
- Review CI release workflows for credentials embedded in repository URLs.
- Inspect recent semantic-release logs and artifacts for unmasked secrets.
- Confirm package-lock or equivalent resolves semantic-release to 19.0.3 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-31051 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N0.73.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.4MediumVector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/semantic-release/semantic-release/security/advisories/GHSA-x2pg-mjhr-2m5xCVE reference · x_refsource_CONFIRM
- https://github.com/semantic-release/semantic-release/commit/58a226f29c04ee56bbb02cc661f020d568849cadCVE reference · x_refsource_MISC
- https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURICVE reference · x_refsource_MISC
- https://github.com/semantic-release/semantic-release/releases/tag/v19.0.3CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.