Skip to main content
VulnerabilityPublished Updated

CVE-2025-55192: JurajNyiri HomeAssistant-Tapo-Control · Code Injection

Affects JurajNyiri HomeAssistant-Tapo-ControlSource CVE Database V5

0

Not known to be exploited · CVSS 8.6 High.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

Organizations should ensure that any usage of the HomeAssistant-Tapo-Control repository is updated to include the patched commit 2a3b80ff128ddf4f410c97dd47a94343792ce43c or later. For repositories with similar GitHub Actions workflows, review and sanitize all user-controlled inputs before use in shell commands. Replace unsafe Bash conditionals with safe quoted grep commands or GitHub Actions expression checks. Limit GitHub Actions workflow permissions to the minimum necessary by using the 'permissions' key with restrictive scopes (e.g., 'permissions: block') to reduce potential damage from compromised workflows. Disable or remove any workflows that process untrusted input without proper validation. Additionally, monitor GitHub Actions logs and audit repository secrets regularly to detect any suspicious activity. Implement strict branch protection rules and require code reviews for workflow changes to prevent introduction of similar vulnerabilities.

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.

References

Community reviews

Loading reviews…