Unauthenticated command execution via OS command injection
Published Apr 16, 2026 · Updated Apr 16, 2026
OS command injection in HGiga iSherlock Base before 476 and Audit before 261 allows local users to execute commands on the server. HGiga and TWCERT/CC have not disclosed the vulnerable interface, parameter, or command-building operation that fails to neutralize input. Access from the local host is required, but authentication is not; successful injection executes commands with the affected service's privileges.
Summary
What happened
OS command injection in HGiga iSherlock Base before 476 and Audit before 261 allows local users to execute commands on the server. HGiga and TWCERT/CC have not disclosed the vulnerable interface, parameter, or command-building operation that fails to neutralize input. Access from the local host is required, but authentication is not; successful injection executes commands with the affected service's privileges.
The record
- CVE
- CVE-2026-6349
- Published
- Apr 16, 2026
- Updated
- Apr 16, 2026
- Vendor
- HGiga
- Product
- iSherlock Audit
- Classifications
- CWE-78, CAPEC-88, T1059.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 2026CVE publishedPublication date reported by the CVE source.
- Apr 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <261
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo