# SUSE-SU-2026:23583-1: Security update for libgpg-error

> An out-of-bounds read in libgpg-error can cause crashes or leak memory when specific flags are used, requiring a patch.

- **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:** 31 Aug 2026

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

SUSE-SU-2026:23583-1 is a memory corruption vulnerability in libgpg-error, published on 31 Aug 2026. 

### Official description

This update for libgpg-error fixes the following issue:

- Out-of-bounds read in `_gpgrt_vfnameconcat` of `stringutils.c` when the `GPGRT_FCONCAT_SYSCONF` flag is used
  (bsc#1263078).

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libgpg-error` | SUSE:Linux Enterprise Server 16.0 | All versions | 1.58-160000.2.1 |
| `libgpg-error` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 1.58-160000.2.1 |

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

Apply the vendor's patch.

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

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2026:23583-1 is a memory corruption vulnerability in libgpg-error, published on 31 Aug 2026. 
Exploitation: There is no known exploitation of SUSE-SU-2026:23583-1 in the wild and no public exploit code.

Affected product: libgpg-error. 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-23583-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2026-23583-1/index.md)
```

## Sources

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

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