H.VIEW IP cameras vulnerable to command injection
Two vulnerabilities in H.VIEW HV-500S6 IP cameras allow authenticated attackers to execute arbitrary code and upload malicious files with persistent system access.
Sourcecisa.gov — open the original
What to check
- Applies to
- The 2 CVEs named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
CISA has disclosed two vulnerabilities affecting H.VIEW HV-500S6 IP cameras running firmware version IPCAM_V4.06.88.251229. CVE-2026-55975 is an OS command injection flaw in the certificate generation interface that allows authenticated users to inject unsanitized XML fields, leading to command execution with elevated privileges. CVE-2026-56414 permits authenticated users to upload arbitrary files to persistent filesystem locations without validation, potentially compromising system integrity across reboots.
Both vulnerabilities require authentication but could enable attackers to gain full control of affected devices. H.VIEW did not respond to CISA's coordination attempts, and no patches are currently available. The devices are deployed worldwide in commercial facilities.
CISA recommends isolating affected cameras from the internet, placing them behind firewalls, and using VPNs for remote access. Organizations should contact H.VIEW directly for support. No active exploitation has been reported to CISA at this time.
Mentioned in this report
Detection guidance
Possible OS Command Injection Attempt Against Embedded Device Web Interface
A behavioural hunt for the technique in general, not a signature for the CVEs this report names.
Detects HTTP requests containing shell metacharacters or command chaining sequences within XML/certificate-related parameters, consistent with the H.VIEW HV-500S6 command injection flaw (CVE-2026-55975) where unsanitized XML fields are passed to a system shell. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: Possible OS Command Injection Attempt Against Embedded Device Web Interface
id: 29871d2c-00b9-53f2-b9cd-b310033ac9c1
status: experimental
description: 'Detects HTTP requests to device management/administration interfaces
(e.g. certificate generation or configuration endpoints) that contain shell metacharacters
or command chaining sequences in request parameters, indicative of OS command injection
attempts such as CVE-2026-55975 affecting H.VIEW IP cameras.
'
references:
- https://www.cisa.gov
author: Vorant
logsource:
category: proxy
detection:
selection:
c-uri|contains:
- cert
- certificate
- config
injection_patterns:
c-uri|contains:
- ;
- '|'
- '`'
- $(
- '&&'
- '||'
- '%0a'
- '%0d'
condition: selection and injection_patterns
falsepositives:
- Legitimate configuration values that happen to contain pipe or semicolon characters
(rare in well-formed XML fields)
- Vulnerability scanners or authorized penetration testing traffic
level: medium
tags:
- attack.t1059
- attack.execution
Suspicious Arbitrary File Upload to Embedded Device Persistent Storage
A behavioural hunt for the technique in general, not a signature for the CVEs this report names.
Detects HTTP POST/multipart upload requests to device administration endpoints delivering files with executable or script extensions, consistent with unauthenticated persistence via arbitrary file upload (CVE-2026-56414) on H.VIEW IP cameras. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: Suspicious Arbitrary File Upload to Embedded Device Persistent Storage
id: 905bab21-3953-5d80-8c53-5d2f67120726
status: experimental
description: 'Detects file upload requests to embedded device (e.g. IP camera) web
management interfaces where the uploaded file has a script or executable extension,
which may indicate exploitation of an unrestricted file upload vulnerability such
as CVE-2026-56414 to plant persistent malicious files on the device filesystem.
'
references:
- https://www.cisa.gov
author: Vorant
logsource:
category: proxy
detection:
selection:
cs-method: POST
c-uri|contains:
- upload
- firmware
- import
suspicious_ext:
c-uri|contains:
- .sh
- .cgi
- .php
- .elf
- .bin
condition: selection and suspicious_ext
falsepositives:
- Legitimate firmware update or configuration import performed by administrators using
expected file types
- Automated device provisioning tools uploading firmware binaries as part of normal
maintenance
level: medium
tags:
- attack.t1105
- attack.command-and-control
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-26-176-05
Free public brief. The detections with Splunk SPL already written (plus Elastic and KQL where they apply) are in the app with a free account, no card. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply) and live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,436 reports from 149 sources, 661 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs