# openSUSE-SU-2026:20803-1: Security update for patterns-glibc-hwcaps

> This update moves a glibc hardware capability pattern to the main repository for performance optimization, with no security vulnerability described.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 9 Apr 2026

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

openSUSE-SU-2026:20803-1 is a vulnerability, published on 9 Apr 2026. 

### Official description

This update for patterns-glibc-hwcaps fixes the following issues:

The pattern is moved from PackageHub to regular SLES.

It requires packages for the x86_64 v3 architecture and is automatically
pulled in when this architecture is present.

These packages are optimized for the x86_64 v3 architecture to increase performance.

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


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

No fix has been published for openSUSE-SU-2026:20803-1 yet. Limit exposure of the affected software until one is available.

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

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

## Fix prompt for AI coding agents

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

What it is: openSUSE-SU-2026:20803-1 is a vulnerability, published on 9 Apr 2026. 
Exploitation: There is no known exploitation of openSUSE-SU-2026:20803-1 in the wild and no public exploit code.

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-20803-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2026-20803-1/index.md)
```

## Sources

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

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