Security readout for executives and security teams
Plain-English summary
A malicious pull request title could make Logto’s Commitlint GitHub Actions job run unintended commands. The impact is constrained to the temporary CI runner: its token was read-only and repository secrets were not exposed. Deployed Logto services are not identified as directly vulnerable.
Executive priority
Prioritize a prompt CI configuration update for teams maintaining Logto repositories or affected forks. This is not presented as a compromise of deployed authentication services, and the runner’s permissions limit impact. Treat it as a moderate software supply-chain and workflow-integrity issue rather than an emergency infrastructure incident.
Technical view
Logto versions 1.40.1 through 1.40.x directly interpolated an untrusted pull request title into an inline shell command in .github/workflows/commitlint.yml. Crafted input could escape the intended string and execute commands on the GitHub Actions runner. Version 1.41.0 fixes the workflow. This is classified as CWE-94 with CVSS 3.1 score 6.3.
Likely exposure
Exposure primarily concerns Logto’s repository workflow and forks or copies retaining the vulnerable Commitlint configuration while accepting untrusted pull requests. Merely running the Logto application does not, from the supplied evidence, establish exposure. The affected range is 1.40.1 through versions before 1.41.0.
Exploitation context
Execution requires attacker-controlled pull request title data to reach the vulnerable workflow. The supplied record is not in KEV and provides no evidence of active exploitation. Potential effects include changing or disrupting the ephemeral workflow, with limited confidentiality, integrity, and availability impact because the token was read-only and secrets were unavailable.
Researcher notes
The affected component is CI workflow logic, not identified Logto runtime code. Scope is unchanged, and the vector requires workflow processing of attacker-controlled pull request metadata. The source bundle documents a read-only token, no repository-secret exposure, an ephemeral runner impact, and a fixed release. No exploit-in-the-wild evidence is supplied.
Mitigation direction
- Update the affected Logto repository or workflow to version 1.41.0 or later.
- Apply the vendor’s workflow correction from the referenced fix commit if upgrading is impractical.
- Check maintained forks and copied workflows for the same unsafe pull request title handling.
- Review current vendor guidance before adopting any alternative mitigation.
Validation and detection
- Confirm the repository version is 1.41.0 or later.
- Inspect .github/workflows/commitlint.yml for direct pull request title interpolation into shell commands.
- Verify maintained forks and workflow copies contain the referenced correction.
- Review relevant Actions history for unexpected Commitlint behavior or runner disruption.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-63187 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
- 6.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
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:L/PR:N/UI:R/S:U/C:L/I:L/A:L2.83.4GitHub_MVulnerability scoring details
Base CVSS 3.1 score
6.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/logto-io/logto/security/advisories/GHSA-869c-8mm3-w5cjCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/logto-io/logto/pull/9112CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/logto-io/logto/commit/4a1cab21c14d26d288ffffc509cc2a8cae247b92CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/logto-io/logto/releases/tag/v1.41.0CVE reference, GitHub_M · 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.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.