CVE-2026-45259

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EPSS
0.7%
KEV
Not listed

Published

June 27, 2026

Last Modified

July 1, 2026

Advisory Details (1)

Auto-updated Jun 29, 2026
No patch confirmed yet.
generic
https://security.freebsd.org/advisories/FreeBSD-SA-26:28.capsicum.asc

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 09:37 UTCEG score recompute
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-11 11:09 UTCEG score recompute
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-10 12:41 UTCEG score recompute
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-09 14:13 UTCEG score recompute
  8. 2026-07-08 15:45 UTCEG score recompute
  9. 2026-07-07 17:16 UTCEG score recompute
  10. 2026-07-07 13:46 UTCEPSS rescore
  11. 2026-07-06 18:37 UTCEG score recompute
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-05 20:08 UTCEG score recompute
  15. 2026-07-04 21:39 UTCEG score recompute
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-03 23:11 UTCEG score recompute
  18. 2026-07-03 00:32 UTCEG score recompute
  19. 2026-07-02 02:03 UTCEG score recompute
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-07-01 03:35 UTCEG score recompute
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 05:07 UTCEG score recompute▲ 6.50
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 7 more
  1. 2026-06-29 13:32 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-27 09:36 UTCNVD update
  6. 2026-06-27 09:15 UTCEG score recompute
  7. 2026-06-27 09:14 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-45259?
CVE-2026-45259 is a medium vulnerability published on June 27, 2026. 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…
When was CVE-2026-45259 disclosed?
CVE-2026-45259 was first published in the National Vulnerability Database on June 27, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45259 actively exploited?
CVE-2026-45259 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45259?
CVE-2026-45259 has a CVSS v3.1 base score of 6.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-45259?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45259, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-45259

Explore →

Is Your Infrastructure Affected by CVE-2026-45259?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs