# CVE-2026-123876: A flaw was found in the default seccomp profile used by Podman via containers-common.


- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 6 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** ALPINE-CVE-2026-123876, AZL-113092, AZL-113095, AZL-113101, AZL-113188, AZL-113191, AZL-113194, DEBIAN-CVE-2026-123876, GHSA-2fgp-24rx-f2r7, UBUNTU-CVE-2026-123876

## What is CVE-2026-123876?

CVE-2026-123876 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 6 Nov 2026. 

### Official description

A flaw was found in the default seccomp profile used by Podman via containers-common. Deny rules for AF_VSOCK and NETLINK_AUDIT compared socket arguments with unmasked 64-bit equality. Because the kernel truncates those int arguments to 32 bits, setting upper bits can bypass the deny rules.

Weakness: CWE-184 (Incomplete List of Disallowed Inputs)

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


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

Upgrade to a fixed version.

## Is CVE-2026-123876 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123876 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123876 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 6 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123876 exists.

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-123876/ (Markdown: https://insights.sbomify.com/CVE-2026-123876/index.md)
```

## Sources

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

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