CVE-2024-58354: Improper Neutralization of Special Elements used in a Command ('Command Injection') in calcom cal.diy
cal.com (calcom repository, later renamed cal.diy) is affected by a repository takeover vulnerability in its GitHub Actions workflows. The workflow pr.yml uses the pull_request_target trigger with the repository's default write permissions and passes them down to check-types.yml. check-types.yml then performs a 'dangerous' checkout of the attacker-submitted pull request code (via the dangerous-git-checkout action) and subsequently executes it (through yarn install and package.json scripts). An attacker can open a pull request whose code runs arbitrary commands with the repository's write-scoped GITHUB_TOKEN, allowing them to push commits, merge or mutate pull requests, add or delete comments, and delete or force-push branches, thereby compromising the repository. The main branch is affected; no patched version is available.
AI Analysis
Technical Summary
The cal.com (cal.diy) repository is vulnerable to a command injection and repository takeover via GitHub Actions workflows. Specifically, the pr.yml workflow uses the pull_request_target trigger with default write permissions, which are passed to check-types.yml. The check-types.yml workflow performs a checkout of attacker-controlled pull request code using the dangerous-git-checkout action and executes it through yarn install and package.json scripts. This execution occurs with the repository's write-scoped GITHUB_TOKEN, enabling an attacker to perform unauthorized repository modifications such as pushing commits, merging pull requests, and deleting branches. The vulnerability affects the main branch, and no official fix or patch has been released.
Potential Impact
An attacker who submits a malicious pull request can execute arbitrary commands within the GitHub Actions environment with write permissions to the repository. This allows them to push commits, merge or alter pull requests, add or remove comments, and delete or force-push branches. Such actions can lead to full repository compromise, including unauthorized code changes and disruption of repository integrity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, repository maintainers should avoid using the pull_request_target trigger with default write permissions for workflows that execute untrusted code. Restrict workflow permissions, avoid executing code from untrusted pull requests, and consider using safer workflow triggers or manual code reviews before merging. Monitor official cal.com advisories for updates and patches.
CVE-2024-58354: Improper Neutralization of Special Elements used in a Command ('Command Injection') in calcom cal.diy
Description
cal.com (calcom repository, later renamed cal.diy) is affected by a repository takeover vulnerability in its GitHub Actions workflows. The workflow pr.yml uses the pull_request_target trigger with the repository's default write permissions and passes them down to check-types.yml. check-types.yml then performs a 'dangerous' checkout of the attacker-submitted pull request code (via the dangerous-git-checkout action) and subsequently executes it (through yarn install and package.json scripts). An attacker can open a pull request whose code runs arbitrary commands with the repository's write-scoped GITHUB_TOKEN, allowing them to push commits, merge or mutate pull requests, add or delete comments, and delete or force-push branches, thereby compromising the repository. The main branch is affected; no patched version is available.
CVSS v4.0
Score 8.5high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The cal.com (cal.diy) repository is vulnerable to a command injection and repository takeover via GitHub Actions workflows. Specifically, the pr.yml workflow uses the pull_request_target trigger with default write permissions, which are passed to check-types.yml. The check-types.yml workflow performs a checkout of attacker-controlled pull request code using the dangerous-git-checkout action and executes it through yarn install and package.json scripts. This execution occurs with the repository's write-scoped GITHUB_TOKEN, enabling an attacker to perform unauthorized repository modifications such as pushing commits, merging pull requests, and deleting branches. The vulnerability affects the main branch, and no official fix or patch has been released.
Potential Impact
An attacker who submits a malicious pull request can execute arbitrary commands within the GitHub Actions environment with write permissions to the repository. This allows them to push commits, merge or alter pull requests, add or remove comments, and delete or force-push branches. Such actions can lead to full repository compromise, including unauthorized code changes and disruption of repository integrity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, repository maintainers should avoid using the pull_request_target trigger with default write permissions for workflows that execute untrusted code. Restrict workflow permissions, avoid executing code from untrusted pull requests, and consider using safer workflow triggers or manual code reviews before merging. Monitor official cal.com advisories for updates and patches.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-06-08T15:20:35.497Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6289ae9c2644c7f8c05b98
Added to database: 07/23/2026, 21:37:50 UTC
Last enriched: 07/23/2026, 21:52:31 UTC
Last updated: 07/24/2026, 00:17:09 UTC
Views: 6
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.