CVE-2026-45259CWE-266

sigqueue(2) missing capability mode restriction

Medium · published June 27, 2026

CVSS v3.1
6.5
EPSS
0%
Percentile
2.5
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
6.5 · MEDIUM
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
CVSS v4.0
Not supplied
EPSS
0.00132 · 2.5th percentile
Weakness
CWE-266 · Incorrect Privilege Assignment
Published
2026-06-27T08:59Z
EPSS history
Timeline
  • 27 JUN 08:59Z
    sigqueue(2) missing capability mode restriction
    cvelistv5