# CVE-2025-55192: HomeAssistant-Tapo-Control Code Injection Vulnerability in issues.yml Workflow

> Attackers can execute arbitrary commands on GitHub Actions runners via malicious issue bodies, potentially exposing repository secrets and contents.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2025
- **Updated:** 12 Sep 2025
- **Also known as:** GHSA-xccg-43hx-c846

## What is CVE-2025-55192?

CVE-2025-55192 is a high-severity code injection vulnerability in JurajNyiri HomeAssistant-Tapo-Control, published on 14 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2025-55192?


## How do I fix CVE-2025-55192?

No fix has been published for CVE-2025-55192 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-55192 being exploited?

There is no known exploitation of CVE-2025-55192 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-55192 and fix it if it is affected.

What it is: CVE-2025-55192 is a high-severity code injection vulnerability in JurajNyiri HomeAssistant-Tapo-Control, published on 14 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-55192 in the wild and no public exploit code.

Affected product: JurajNyiri HomeAssistant-Tapo-Control. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-55192/ (Markdown: https://insights.sbomify.com/CVE-2025-55192/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-55192
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-55192
- OSV: https://osv.dev/vulnerability/CVE-2025-55192

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-55192/
Summaries are generated and may contain mistakes; the official description above is the record.