CVE-2026-45259
sigqueue(2) missing capability mode restriction
Description
sigqueue(2) was marked as permitted in capability mode with the introduction of Capsicum in 2011, but the implementation of kern_sigqueue did not include a capability mode check restricting signal delivery to the calling process's own PID. A process in capability mode can use sigqueue(2) to send signals to any process it could signal following standard Unix permissions, bypassing the Capsicum sandbox restriction. A compromised sandboxed process could interfere with other processes, for example by sending SIGKILL or SIGSTOP. This could be any process running as the same user, or any process, for a superuser sandboxed process.
INFO
Published Date :
June 27, 2026, 8:59 a.m.
Last Modified :
June 27, 2026, 8:59 a.m.
Remotely Exploit :
No
Source :
freebsd
Affected Products
The following products are affected by CVE-2026-45259
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update the system kernel and related security components.
- Verify sigqueue() respects capability mode restrictions.
- Test signal delivery for sandboxed processes.
- Reboot the system after applying updates.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-45259 vulnerability anywhere in the article.