CVE-2026-63187: CWE-94: Improper Control of Generation of Code ('Code Injection') in logto-io logto
A code injection vulnerability (CWE-94) exists in logto versions from 1.40.1 up to but not including 1.41.0. The vulnerability arises from unsafe interpolation of the GitHub pull request title into a shell command within the GitHub Actions workflow, allowing injection of arbitrary shell commands. The injected commands run with a read-only GITHUB_TOKEN and do not expose repository secrets but can disrupt or alter the ephemeral workflow execution. This issue is fixed in version 1.41.0.
AI Analysis
Technical Summary
Logto versions >=1.40.1 and <1.41.0 contain a code injection vulnerability in the GitHub Actions workflow file .github/workflows/commitlint.yml. The workflow directly interpolates the pull request title into an inline echo command that pipes to npx commitlint. If the pull request title contains a single quote, it can terminate the echo string and append arbitrary shell commands executed on the GitHub Actions runner. The injected commands run with a read-only GITHUB_TOKEN and do not have access to repository secrets, limiting impact to disruption or alteration of the ephemeral workflow execution environment. The vulnerability is resolved in version 1.41.0.
Potential Impact
An attacker who can control the pull request title can inject arbitrary shell commands into the GitHub Actions workflow execution environment. Although the GITHUB_TOKEN is read-only and repository secrets are not exposed, injected commands can disrupt or alter the workflow execution, potentially causing denial of service or other unintended side effects during CI runs. There is no direct impact on repository secrets or persistent codebase compromise.
Mitigation Recommendations
Upgrade to logto version 1.41.0 or later, where this issue is fixed. Since the vulnerability is in the GitHub Actions workflow, ensure that workflows do not directly interpolate untrusted input into shell commands. No additional mitigation is required if the upgrade is applied.
CVE-2026-63187: CWE-94: Improper Control of Generation of Code ('Code Injection') in logto-io logto
Description
A code injection vulnerability (CWE-94) exists in logto versions from 1.40.1 up to but not including 1.41.0. The vulnerability arises from unsafe interpolation of the GitHub pull request title into a shell command within the GitHub Actions workflow, allowing injection of arbitrary shell commands. The injected commands run with a read-only GITHUB_TOKEN and do not expose repository secrets but can disrupt or alter the ephemeral workflow execution. This issue is fixed in version 1.41.0.
CVSS v3.1
Score 6.3medium
Affected software
pkg:github/logto-io/logtoRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Logto versions >=1.40.1 and <1.41.0 contain a code injection vulnerability in the GitHub Actions workflow file .github/workflows/commitlint.yml. The workflow directly interpolates the pull request title into an inline echo command that pipes to npx commitlint. If the pull request title contains a single quote, it can terminate the echo string and append arbitrary shell commands executed on the GitHub Actions runner. The injected commands run with a read-only GITHUB_TOKEN and do not have access to repository secrets, limiting impact to disruption or alteration of the ephemeral workflow execution environment. The vulnerability is resolved in version 1.41.0.
Potential Impact
An attacker who can control the pull request title can inject arbitrary shell commands into the GitHub Actions workflow execution environment. Although the GITHUB_TOKEN is read-only and repository secrets are not exposed, injected commands can disrupt or alter the workflow execution, potentially causing denial of service or other unintended side effects during CI runs. There is no direct impact on repository secrets or persistent codebase compromise.
Mitigation Recommendations
Upgrade to logto version 1.41.0 or later, where this issue is fixed. Since the vulnerability is in the GitHub Actions workflow, ensure that workflows do not directly interpolate untrusted input into shell commands. No additional mitigation is required if the upgrade is applied.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-15T22:13:00.721Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a86e0f8acd9273b498385ce
Added to database: 08/20/2026, 11:11:52 UTC
Last enriched: 08/20/2026, 11:22:25 UTC
Last updated: 08/20/2026, 11:22:25 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.