# openSUSE-SU-2026:21040-1: Security update for sg3_utils

> An attacker can execute arbitrary commands via unquoted variables in the rescan-scsi-bus.sh script, requiring local access or specific SCSI bus interactions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jun 2026

## What is openSUSE-SU-2026:21040-1?

openSUSE-SU-2026:21040-1 is a command injection vulnerability in sg3_utils, published on 23 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This update for sg3_utils fixes the following issues:

- sg_inq: --export output conformance for SCSI name string and ATA fields (bsc#1267823)
- rescan-scsi-bus.sh: quote $id_serial in findmultipath call (bsc#1268201)

## Which versions are affected by openSUSE-SU-2026:21040-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sg3_utils` | openSUSE:Leap 16.0 | All versions | 1.48~20221101+7.f75279c0-160000.1.1 |

## How do I fix openSUSE-SU-2026:21040-1?

Apply the vendor's patch.

## Is openSUSE-SU-2026:21040-1 being exploited?

There is no known exploitation of openSUSE-SU-2026:21040-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for openSUSE-SU-2026:21040-1 and fix it if it is affected.

What it is: openSUSE-SU-2026:21040-1 is a command injection vulnerability in sg3_utils, published on 23 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of openSUSE-SU-2026:21040-1 in the wild and no public exploit code.

Affected product: sg3_utils. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/openSUSE-SU-2026-21040-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2026-21040-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2026:21040-1

---
From sbomify Insights: https://insights.sbomify.com/openSUSE-SU-2026-21040-1/
Summaries are generated and may contain mistakes; the official description above is the record.