CVE-2026-45256

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory published 2026-06-26. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

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

When used to deliver a signal to a specific thread, thr_kill2(2) called p_cansignal() to determine whether the operation was permitted but did not check the result before delivering the signal. The signal was sent even when the permission check failed. The system call returned the resulting error to the caller, but by then the signal had already been delivered.

The missing check allows an unprivileged local user who knows or can guess a target's process and thread IDs to send any signal to a process they would not normally be permitted to signal, including processes owned by other users or by root. The same check enforces jail boundaries, so a jailed process can signal processes on the host or in other jails. Thread IDs are allocated globally and sequentially, and so can be discovered by brute force with no visibility into the target.

An attacker can stop or terminate arbitrary processes, including critical system daemons, resulting in a Denial of Service (DoS).

CVSS v3
5.5
EG Score
5.5(high)
EPSS
0.6%
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-45256(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 31× 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-07 06:01 UTCEG score recompute
  2. 2026-07-07 06:01 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 08:00 UTCEG score recompute
  5. 2026-07-06 08:00 UTCGHSA enrichment
  6. 2026-07-05 09:57 UTCEG score recompute
  7. 2026-07-05 09:57 UTCGHSA enrichment
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 11:56 UTCEG score recompute
  10. 2026-07-04 11:56 UTCGHSA enrichment
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 13:56 UTCEG score recompute
  13. 2026-07-03 13:56 UTCGHSA enrichment
  14. 2026-07-02 15:57 UTCEG score recompute
  15. 2026-07-02 15:57 UTCGHSA enrichment
  16. 2026-07-01 17:57 UTCEG score recompute
  17. 2026-07-01 17:56 UTCGHSA enrichment
  18. 2026-07-01 15:07 UTCEPSS rescore
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-30 19:56 UTCEG score recompute
  21. 2026-06-30 19:56 UTCGHSA enrichment
  22. 2026-06-29 21:56 UTCEG score recompute 5.50
  23. 2026-06-29 21:56 UTCGHSA enrichment
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 6 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-26 17:41 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  5. 2026-06-26 15:44 UTCEG score recompute
  6. 2026-06-26 15:44 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-45256?
CVE-2026-45256 is a medium vulnerability published on June 26, 2026. When used to deliver a signal to a specific thread, thrkill2(2) called pcansignal() to determine whether the operation was permitted but did not check the result before delivering the signal. The signal was sent even when the permission check failed. The system call returned the resulting error to…
When was CVE-2026-45256 disclosed?
CVE-2026-45256 was first published in the National Vulnerability Database on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45256 actively exploited?
CVE-2026-45256 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45256?
CVE-2026-45256 has a CVSS v3.1 base score of 5.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-45256?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45256, 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-45256

Explore →

Is Your Infrastructure Affected by CVE-2026-45256?

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