{"api_version":"1","generated_at":"2026-06-27T18:33:05+00:00","cve":"CVE-2026-45259","urls":{"html":"https://cve.report/CVE-2026-45259","api":"https://cve.report/api/cve/CVE-2026-45259.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-45259","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-45259"},"summary":{"title":"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.\n\nA 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.","state":"PUBLISHED","assigner":"freebsd","published_at":"2026-06-27 09:16:22","updated_at":"2026-06-27 09:16:22"},"problem_types":["CWE-266","CWE-266 CWE-266: Incorrect Privilege Assignment"],"metrics":[],"references":[{"url":"https://security.freebsd.org/advisories/FreeBSD-SA-26:28.capsicum.asc","name":"https://security.freebsd.org/advisories/FreeBSD-SA-26:28.capsicum.asc","refsource":"secteam@freebsd.org","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-45259","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45259","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"FreeBSD","product":"FreeBSD","version":"affected 15.0-RELEASE p10 release","platforms":[]},{"source":"CNA","vendor":"FreeBSD","product":"FreeBSD","version":"affected 14.4-RELEASE p6 release","platforms":[]},{"source":"CNA","vendor":"FreeBSD","product":"FreeBSD","version":"affected 14.3-RELEASE p15 release","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"Ed Maste","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unknown","modules":["capsicum"],"product":"FreeBSD","vendor":"FreeBSD","versions":[{"lessThan":"p10","status":"affected","version":"15.0-RELEASE","versionType":"release"},{"lessThan":"p6","status":"affected","version":"14.4-RELEASE","versionType":"release"},{"lessThan":"p15","status":"affected","version":"14.3-RELEASE","versionType":"release"}]}],"credits":[{"lang":"en","type":"finder","value":"Ed Maste"}],"datePublic":"2026-06-09T23:30:00.000Z","descriptions":[{"lang":"en","value":"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.\n\nA 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."}],"problemTypes":[{"descriptions":[{"cweId":"CWE-266","description":"CWE-266: Incorrect Privilege Assignment","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-06-27T08:59:17.853Z","orgId":"63664ac6-956c-4cba-a5d0-f46076e16109","shortName":"freebsd"},"references":[{"tags":["vendor-advisory"],"url":"https://security.freebsd.org/advisories/FreeBSD-SA-26:28.capsicum.asc"}],"title":"sigqueue(2) missing capability mode restriction","x_generator":{"engine":"cvelib 1.8.0"}}},"cveMetadata":{"assignerOrgId":"63664ac6-956c-4cba-a5d0-f46076e16109","assignerShortName":"freebsd","cveId":"CVE-2026-45259","datePublished":"2026-06-27T08:59:17.853Z","dateReserved":"2026-05-11T16:27:44.892Z","dateUpdated":"2026-06-27T08:59:17.853Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-06-27 09:16:22","lastModifiedDate":"2026-06-27 09:16:22","problem_types":["CWE-266","CWE-266 CWE-266: Incorrect Privilege Assignment"],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"45259","Ordinal":"1","Title":"sigqueue(2) missing capability mode restriction","CVE":"CVE-2026-45259","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"45259","Ordinal":"1","NoteData":"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.\n\nA 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.","Type":"Description","Title":"sigqueue(2) missing capability mode restriction"}]}}}