# SUSE-SU-2026:22069-1: Security update for rpcbind

> An attacker can exploit buffer overflows and memory leaks in rpcbind to execute arbitrary code or cause denial of service.

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

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

SUSE-SU-2026:22069-1 is a memory corruption vulnerability in rpcbind, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for rpcbind fixes the following issues
  
Update to rpcbind 1.2.9:

Security issue:

- Fix several memory leaks and buffer overflows (bsc#1267212).

Non security issue:

- rpcbind fails to start (tumbleweed snapshot 20181120) (bsc#1117217).

Changes:

 * rpcinfo: stack buffer overflow in rpcinfo rpcbaddrlist()
 * rpcbind: Stop unauthenticated oversized allocation in PMAPPROC_CALLIT decode
 * rpcbind: fix memory leak in read_warmstart()
 * rpcbind: fix memory leaks in network_init()
 * rpcbind: fix memory leak in init_transport()
 * Added -v (print version and compile flags)
 * rpcinfo: Removed a number of "old-style function definition" warnings
 * man/rpcbind: Update list of options
 * Comment out ListenStream=@/run/rpcbind.sock
 * [nfs/nfs-utils/rpcbind] rpcbind: avoid dereferencing NULL from realloc()
 * systemd/rpcbind.service.in: Add various hardenings options
 * man/rpcbind: Add Files section to manpage
 * Moved rpcbind.lock and default configs to /run instead of /var/run
 * rpcinfo: try connecting using abstract address
 * Listen on an AF_UNIX abstract address if supported
 * autotools/systemd: call rpcbind with -w only on enabled warm starts
 * rpcbind: fix double free in init_transport

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rpcbind` | SUSE:Linux Micro 6.1 | All versions | 1.2.9-slfo.1.1_1.1 |

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

Apply the vendor's patch.

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

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2026:22069-1 is a memory corruption vulnerability in rpcbind, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2026:22069-1 in the wild and no public exploit code.

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

## Sources

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

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