CVE-2026-16313

What it is

A flaw was found in sg3_utils. The sg_inq command, when invoked with the --export option, outputs device identification data without sanitizing control characters in SCSI name string fields. A newline character embedded in a device-supplied name string can inject arbitrary properties into the udev device database. This could allow an attacker who can present a crafted SCSI device to execute arbitrary commands as root when the device is disconnected.

At a glance

Exploitability

Can be exploited with physical access without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-07-28 17:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-11-09 17:17 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 7.6 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-07-28 17:16 UTC

Last modified

2026-11-09 17:17 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-93

Record status

Awaiting Analysis

Attack profile CVSS 3.1 · 7.6

Attack vector

Physical

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-16313.md and follow it. Check whether this project is affected by CVE-2026-16313. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge