Seccomp: denylist bypass

Seccomp

A seccomp filter bypass pattern has been discovered, affecting several projects including containerd, Podman, systemd, and QEMU.

Do this now

No source names a fix yet: limit who can reach Seccomp until one does.

First seen: 27 Oct 2026
Last update: 27 Oct 2026, 21:18 UTC
Source: news

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## Seccomp: denylist bypass
Severity: unknown. Patch status: fix status unknown.
Affected: Seccomp

A seccomp filter bypass pattern has been discovered, affecting several projects including containerd, Podman, systemd, and QEMU.

## Steps
1. Search the repo, its CI and infra config for Seccomp. If present, report the version in use and whether it's affected.
2. No source names a fix yet; check the vendor advisory. Until one ships: restrict network access to it.

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://seclists.org/oss-sec/2026/q4/400
https://pwned.coffee/i/seccomp-denylist-bypass

Receipt

Exploitation: No known exploitation
Score: No CVSS published yet: severity unknown.
Last checked: 27 Oct 2026, 22:18 UTC

Sources: KEV – CVE record – Vendor –

Sources

seclists.org: Seccomp denylist bypass via 32-bit syscall argument truncation

Wrong fix version, or a source we missed? Send it back to chef@pwned.coffee with the source, and we'll correct it here.

Totalone coffee