Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2026-45256


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).


Security Impact Summary

This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 5.5, requiring local system access to exploit with relatively low complexity without requiring user interaction requiring only low-level privileges . The vulnerability impacts and availability (service disruption) for affected systems. Impacting 1 product from freebsd organizations running these solutions should prioritize assessment and patching.

Historical Context

Reported in 2026, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.


Published

2026-06-26T15:16:39.170

Last Modified

2026-06-26T18:58:48.590

Status

Analyzed

Source

[email protected]

Severity

CVSSv3.1: 5.5 (MEDIUM)

Weaknesses
  • Type: Secondary
    CWE-269

Affected Vendors & Products
Type Vendor Product Version/Range Vulnerable?
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.1 Yes

References

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For freebsd's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.