# SUSE-SU-2026:2687-1: Security update for sg3_utils

> This update fixes output conformance issues in sg_inq for SCSI and ATA fields, requiring users to update the sg3_utils package.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jun 2026

## What is SUSE-SU-2026:2687-1?

SUSE-SU-2026:2687-1 is a vulnerability in sg3_utils, published on 30 Jun 2026. 

### Official description

This update for sg3_utils fixes the following issue
  
Update to version 1.44~763+20.e416e091:

- sg_inq: --export output conformance for SCSI name string and ATA fields (bsc#1267823).

## Which versions are affected by SUSE-SU-2026:2687-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sg3_utils` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 1.44~763+20.e416e091-150000.9.6.1 |

## How do I fix SUSE-SU-2026:2687-1?

Apply the vendor's patch.

## Is SUSE-SU-2026:2687-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2026:2687-1 is a vulnerability in sg3_utils, published on 30 Jun 2026. 
Exploitation: There is no known exploitation of SUSE-SU-2026:2687-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/SUSE-SU-2026-2687-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2026-2687-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2026:2687-1

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