CVE-2026-63187
What it is
Logto is the modern, open-source auth infrastructure for SaaS and AI apps. From 1.40.1 until 1.41.0, Logto's .github/workflows/commitlint.yml directly interpolated github.event.pull_request.title into the Commitlint on PR title step's inline echo command before piping the title to npx commitlint. A pull request title containing a single quote could terminate the echo string and append arbitrary shell commands on the GitHub Actions runner. The pull_request trigger used a read-only GITHUB_TOKEN and did not expose repository secrets, but injected commands could alter or disrupt the ephemeral workflow execution. This issue is fixed in version 1.41.0.
At a glance
- Exploitability
- Can be exploited over the network without logging in, but needs a user to act. Limited direct impact.
- Exploit odds
- 0.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.4% in the next 30 days (EPSS).
- Severity: 6.3 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.4% · EPSS, next 30 days
- Weakness
- CWE-94 · Code injection
- Record status
- Deferred
Attack profile CVSS 3.1 · 6.3
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-63187.md and follow it. Check whether this project is affected by CVE-2026-63187. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/logto-io/logto/commit/4a1cab21c14d26d288ffffc509cc2a8cae247b92
- https://github.com/logto-io/logto/pull/9112
- https://github.com/logto-io/logto/releases/tag/v1.41.0
- https://github.com/logto-io/logto/security/advisories/GHSA-869c-8mm3-w5cj
- https://github.com/logto-io/logto/security/advisories/GHSA-869c-8mm3-w5cj
References
- https://github.com/logto-io/logto/commit/4a1cab21c14d26d288ffffc509cc2a8cae247b92
- https://github.com/logto-io/logto/pull/9112
- https://github.com/logto-io/logto/releases/tag/v1.41.0
- https://github.com/logto-io/logto/security/advisories/GHSA-869c-8mm3-w5cj
- https://github.com/logto-io/logto/security/advisories/GHSA-869c-8mm3-w5cj