CVE-2026-27701: CWE-94: Improper Control of Generation of Code ('Code Injection') in live-codes livecodes
LiveCode is an open-source, client-side code playground. Prior to commit e151c64c2bd80d2d53ac1333f1df9429fe6a1a11, LiveCode's `i18n-update-pull` GitHub Actions workflow is vulnerable to JavaScript injection. The title of the Pull Request associated with the triggering issue comment is interpolated directly into a `actions/github-script` JavaScript block using a GitHub Actions template expression. An attacker who opens a PR with a crafted title can inject arbitrary JavaScript that executes with the privileges of the CI bot token (`CI_APP_ID` / `CI_APP_PRIVATE_KEY`), enabling exfiltration of repository secrets and unauthorized GitHub API operations. Commit e151c64c2bd80d2d53ac1333f1df9429fe6a1a11 fixes the issue.
AI Analysis
Technical Summary
CVE-2026-27701 is a critical code injection vulnerability classified under CWE-94, affecting the LiveCode open-source project, specifically its GitHub Actions workflow named `i18n-update-pull`. The vulnerability arises because the workflow directly interpolates the pull request title into a JavaScript block executed by the `actions/github-script` action without proper sanitization or validation. This unsafe interpolation enables an attacker who can open a pull request to inject arbitrary JavaScript code. The injected code runs with the privileges of the CI bot token, which includes `CI_APP_ID` and `CI_APP_PRIVATE_KEY`, granting extensive access to repository secrets and the ability to perform unauthorized GitHub API operations. This could include modifying repository content, accessing sensitive data, or disrupting CI/CD processes. The vulnerability was fixed in commit e151c64c2bd80d2d53ac1333f1df9429fe6a1a11 by properly sanitizing or removing unsafe interpolation. The CVSS 4.0 vector indicates network attack vector, high attack complexity, partial user interaction, no privileges required, and high impact on confidentiality, integrity, and availability. Although no exploits have been reported in the wild yet, the nature of the vulnerability and the privileges involved make it a significant risk for organizations using LiveCode's GitHub workflows.
Potential Impact
The impact of CVE-2026-27701 is substantial for organizations using LiveCode and its GitHub Actions workflows. Successful exploitation allows attackers to execute arbitrary JavaScript code within the CI environment, leveraging the CI bot token privileges. This can lead to unauthorized access and exfiltration of sensitive repository secrets such as API keys, credentials, and tokens. Attackers could manipulate repository contents, inject malicious code into the software supply chain, disrupt CI/CD pipelines, or perform further lateral movement within the development environment. The compromise of CI tokens can also affect other integrated services relying on these credentials. Given the widespread use of GitHub Actions and the critical role of CI/CD in modern software development, this vulnerability poses a risk to software integrity, confidentiality, and availability, potentially impacting software supply chain security and trust.
Mitigation Recommendations
To mitigate CVE-2026-27701, organizations should immediately update LiveCode to versions including or after commit e151c64c2bd80d2d53ac1333f1df9429fe6a1a11 where the vulnerability is fixed. Review and sanitize all user-controlled inputs in GitHub Actions workflows, especially those interpolated into scripts or commands. Limit the permissions of CI bot tokens to the minimum necessary scope, avoiding overly broad access to repository secrets or API operations. Implement strict branch protection and pull request review policies to restrict who can open or merge pull requests. Consider using GitHub Actions features like 'workflow_run' triggers or separate workflows with reduced privileges for untrusted contributions. Monitor repository audit logs and CI environment for unusual activity. Rotate any potentially exposed secrets and tokens. Employ static analysis or code scanning tools to detect unsafe code injection patterns in workflows. Educate developers and DevOps teams about secure CI/CD practices and the risks of code injection in automation scripts.
Affected Countries
United States, Germany, United Kingdom, Canada, France, Australia, Japan, Netherlands, India, Brazil
CVE-2026-27701: CWE-94: Improper Control of Generation of Code ('Code Injection') in live-codes livecodes
Description
LiveCode is an open-source, client-side code playground. Prior to commit e151c64c2bd80d2d53ac1333f1df9429fe6a1a11, LiveCode's `i18n-update-pull` GitHub Actions workflow is vulnerable to JavaScript injection. The title of the Pull Request associated with the triggering issue comment is interpolated directly into a `actions/github-script` JavaScript block using a GitHub Actions template expression. An attacker who opens a PR with a crafted title can inject arbitrary JavaScript that executes with the privileges of the CI bot token (`CI_APP_ID` / `CI_APP_PRIVATE_KEY`), enabling exfiltration of repository secrets and unauthorized GitHub API operations. Commit e151c64c2bd80d2d53ac1333f1df9429fe6a1a11 fixes the issue.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-27701 is a critical code injection vulnerability classified under CWE-94, affecting the LiveCode open-source project, specifically its GitHub Actions workflow named `i18n-update-pull`. The vulnerability arises because the workflow directly interpolates the pull request title into a JavaScript block executed by the `actions/github-script` action without proper sanitization or validation. This unsafe interpolation enables an attacker who can open a pull request to inject arbitrary JavaScript code. The injected code runs with the privileges of the CI bot token, which includes `CI_APP_ID` and `CI_APP_PRIVATE_KEY`, granting extensive access to repository secrets and the ability to perform unauthorized GitHub API operations. This could include modifying repository content, accessing sensitive data, or disrupting CI/CD processes. The vulnerability was fixed in commit e151c64c2bd80d2d53ac1333f1df9429fe6a1a11 by properly sanitizing or removing unsafe interpolation. The CVSS 4.0 vector indicates network attack vector, high attack complexity, partial user interaction, no privileges required, and high impact on confidentiality, integrity, and availability. Although no exploits have been reported in the wild yet, the nature of the vulnerability and the privileges involved make it a significant risk for organizations using LiveCode's GitHub workflows.
Potential Impact
The impact of CVE-2026-27701 is substantial for organizations using LiveCode and its GitHub Actions workflows. Successful exploitation allows attackers to execute arbitrary JavaScript code within the CI environment, leveraging the CI bot token privileges. This can lead to unauthorized access and exfiltration of sensitive repository secrets such as API keys, credentials, and tokens. Attackers could manipulate repository contents, inject malicious code into the software supply chain, disrupt CI/CD pipelines, or perform further lateral movement within the development environment. The compromise of CI tokens can also affect other integrated services relying on these credentials. Given the widespread use of GitHub Actions and the critical role of CI/CD in modern software development, this vulnerability poses a risk to software integrity, confidentiality, and availability, potentially impacting software supply chain security and trust.
Mitigation Recommendations
To mitigate CVE-2026-27701, organizations should immediately update LiveCode to versions including or after commit e151c64c2bd80d2d53ac1333f1df9429fe6a1a11 where the vulnerability is fixed. Review and sanitize all user-controlled inputs in GitHub Actions workflows, especially those interpolated into scripts or commands. Limit the permissions of CI bot tokens to the minimum necessary scope, avoiding overly broad access to repository secrets or API operations. Implement strict branch protection and pull request review policies to restrict who can open or merge pull requests. Consider using GitHub Actions features like 'workflow_run' triggers or separate workflows with reduced privileges for untrusted contributions. Monitor repository audit logs and CI environment for unusual activity. Rotate any potentially exposed secrets and tokens. Employ static analysis or code scanning tools to detect unsafe code injection patterns in workflows. Educate developers and DevOps teams about secure CI/CD practices and the risks of code injection in automation scripts.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-23T17:56:51.202Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 699f183fb7ef31ef0b2eb1c9
Added to database: 2/25/2026, 3:41:51 PM
Last enriched: 3/4/2026, 6:57:04 PM
Last updated: 4/11/2026, 11:52:56 PM
Views: 92
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.