CVE-2025-55192: GHSL-2025-101: Code injection in a GitHub Actions workflow of homeassistant-tapo-control - CVE-2025-55192

Published Aug 14, 2025
·
Updated

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.

Other sources

The homeassistant-tapo-control repository was vulnerable to code injection in the issues.yml GitHub Actions workflow.

GitHub Security Lab

Affected Software

1 affected component
Home Assistant homeassistant-tapo-control<2a3b80f

Event History

Aug 14, 2025
CVE Published
via MITRE·04:40 PM
Data Sourced
via MITRE·04:40 PM
DescriptionWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeakness
Sep 11, 2025
Advisory Published
via GitHub Security Lab·12:00 AM
Data Sourced
via GitHub Security Lab·12:00 AM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-55192?

CVE-2025-55192 is classified as a code injection vulnerability affecting the GitHub Actions workflow.

2

How do I fix CVE-2025-55192?

To fix CVE-2025-55192, update HomeAssistant-Tapo-Control to at least version 2a3b80f or later.

3

What software is affected by CVE-2025-55192?

CVE-2025-55192 affects HomeAssistant-Tapo-Control versions prior to commit 2a3b80f.

4

Does CVE-2025-55192 impact end users of Home Assistant?

No, CVE-2025-55192 does not affect users of the Home Assistant integration itself.

5

What type of vulnerability is CVE-2025-55192?

CVE-2025-55192 is identified as a code injection vulnerability in the pipeline configuration.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203