Root command execution via udev property injection
Published Jul 28, 2026 · Updated Aug 31, 2026
Command injection in sg3_utils 1.34 through 1.48 allows physically proximate attackers to execute commands as root via a crafted SCSI device. The export_dev_ids() path prints device-controlled VPD page 0x83 name and ATA fields without escaping newlines, allowing a second udev property such as REMOVE_CMD to be injected. Exploitation requires a system whose udev rules import sg_inq --export output and execute REMOVE_CMD when the attached device is disconnected.
Summary
What happened
Command injection in sg3_utils 1.34 through 1.48 allows physically proximate attackers to execute commands as root via a crafted SCSI device. The export_dev_ids() path prints device-controlled VPD page 0x83 name and ATA fields without escaping newlines, allowing a second udev property such as REMOVE_CMD to be injected. Exploitation requires a system whose udev rules import sg_inq --export output and execute REMOVE_CMD when the attached device is disconnected.
The record
- CVE
- CVE-2026-16313
- Published
- Jul 28, 2026
- Updated
- Aug 31, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions
- Classifications
- CWE-93, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 31, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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