# CVE-2026-16277: Rpcbind: rpcbind: stack buffer overflow in rpcinfo rpcbaddrlist()

> A stack buffer overflow in the rpcinfo utility allows a malicious server to crash the client, causing denial of service on Linux systems.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** AZL-93009, BELL-CVE-2026-16277, DEBIAN-CVE-2026-16277, ECHO-7a2c-85d2-41e3, GHSA-mjwp-v273-38g8, UBUNTU-CVE-2026-16277

## What is CVE-2026-16277?

CVE-2026-16277 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A stack-based buffer overflow was found in rpcbind's rpcinfo utility. When querying a remote rpcbind service with `rpcinfo -l`, address information returned by the server is copied into a fixed-size buffer without sufficient bounds checking. A malicious or compromised rpcbind server could use this flaw to crash the rpcinfo client, resulting in a denial of service. The highest threat from this vulnerability is to system availability.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-16277?


## How do I fix CVE-2026-16277?

Apply the vendor's patch.

## Is CVE-2026-16277 being exploited?

There is no known exploitation of CVE-2026-16277 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16277 and fix it if it is affected.

What it is: CVE-2026-16277 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-16277 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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/CVE-2026-16277/ (Markdown: https://insights.sbomify.com/CVE-2026-16277/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16277
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16277
- OSV: https://osv.dev/vulnerability/CVE-2026-16277

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