CVE-2025-55192 Details
Description
HomeAssistant-Tapo-Control offers Control for Tapo cameras as a Home Assistant component. Prior to commit 2a3b80f, there is a code injection vulnerability in the GitHub Actions workflow .github/workflows/issues.yml. It does not affect users of the Home Assistant integration itself — it only impacts the GitHub Actions environment for this repository. The vulnerable workflow directly inserted user-controlled content from the issue body (github.event.issue.body) into a Bash conditional without proper sanitization. A malicious GitHub user could craft an issue body that executes arbitrary commands on the GitHub Actions runner in a privileged context whenever an issue is opened. The potential impact is limited to the repository’s CI/CD environment, which could allow access to repository contents or GitHub Actions secrets. This issue has been patched via commit 2a3b80f. Workarounds involve disabling the affected workflow (issues.yml), replacing the unsafe Bash comparison with a safe quoted grep (or a pure GitHub Actions expression check), or ensuring minimal permissions in workflows (permissions: block) to reduce possible impact.
A code injection vulnerability has been identified in the GitHub Actions workflow of the HomeAssistant-Tapo-Control repository, specifically in the .github/workflows/issues.yml file. This vulnerability arises from the workflow's improper handling of user-controlled content from issue bodies, which was directly inserted into a Bash conditional without adequate sanitization. As a result, a malicious GitHub user could craft an issue that executes arbitrary commands on the GitHub Actions runner with elevated privileges, potentially accessing repository contents or GitHub Actions secrets. It is important to note that this vulnerability does not affect users of the Home Assistant integration itself, but is confined to the GitHub Actions environment of this repository.
The vulnerability has been patched in commit 2a3b80f. Repositories with the same workflow should update .github/workflows/issues.yml to match the patched version. If immediate upgrading is not possible, the affected workflow can be disabled or the unsafe Bash comparison replaced with a safe, quoted grep or a pure GitHub Actions expression check. Additionally, ensuring minimal permissions in workflows can help reduce the possible impact.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Aug 14, 2025CISA-ADP
Assessed Aug 14, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-94 | Improper Control of Generation of Code ('Code Injection') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| JurajNyiri HomeAssistant-Tapo-Control | All versions |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Sep 12, 2025 | CVE Modified | [email protected] |
| Aug 14, 2025 | New CVE Received | [email protected] |
Volerion