Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain unprivileged user account in FreeBSD jail
-
DeliveryConfirm debug permission on target process
-
ExploitIdentify active jailed root ktrace session on target
-
ExecutionInvoke ktrace flag modification exploiting PRIV_KTRACE denial bug
-
PersistClear or alter tracing flags for target process
-
ImpactAudit trail for target process silently disabled
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V8 - Authorization Privilege drop verification
|
| Exploitation Conditions | Exploitation requires all of the following specific conditions: the attacker must be an existing user account inside a FreeBSD jail (not on the bare host or a different jail); the attacker must have been granted permission to debug the specific target process (e.g., via ptrace, a non-default privilege typically granted explicitly by jail or host administrator); the target host must be running FreeBSD 15.0-RELEASE before p12 or FreeBSD 15.1-RELEASE before p2; and jailed root must have an active ktrace session on that process. Exploitation is strictly limited to within the affected jail - the host system and sibling jails are unaffected. Deployments not using FreeBSD jails are entirely unaffected. Jails where unprivileged users are not granted debug/ptrace capabilities (the default hardened configuration) are not exploitable. |
| Impact | The NVD-assigned CVSS 3.1 score of 8.1 with AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H likely overstates practical severity because A:H is difficult to justify when the impact is confined to disabling tracing within a single jail rather than degrading the host system. The network attack vector is plausible if the attacker accesses the jail via SSH, but exploitation still requires holding debug permission over the specific target process - a non-default, administrator-granted capability. The EPSS score of 0.18% at the 8th percentile is consistent with a low-exploitation-probability privilege logic bug requiring specific jail conditions. There is no CISA KEV listing and no public POC. The primary real-world risk is to audit integrity: even a mid-sized municipal IT team in tczew running FreeBSD jail infrastructure for multi-tenant hosting or security-sensitive workloads should treat this as a priority maintenance patch rather than an emergency, particularly if ktrace is part of their incident response or compliance trail. CVSS overstates availability impact and the low EPSS corroborates that this is not being exploited opportunistically. |
| Exploit ScenarioDerived | An attacker with an unprivileged user account inside a FreeBSD 15.x jail who has been granted debug access to a target process recognizes that jailed root's ktrace session on that same process is not marked privileged due to the PRIV_KTRACE regression. The attacker issues a ktrace flag modification call to clear or alter the jailed root's trace configuration, silently disabling audit capture for that process without triggering a privilege denial. No public exploit code or POC has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 27, 2026
Privilege management regression in FreeBSD 15.x ktrace(2) allows an unprivileged jail user to manipulate or suppress the jailed root user's kernel tracing configuration. Because an unrelated code change inadvertently causes PRIV_KTRACE to always be denied to jailed root, that user's active trace sessions are not marked as privileged - permitting any jail user holding debug rights over a traced process to alter or clear those trace flags. No public exploit has been identified and the EPSS score of 0.18% (8th percentile) reflects negligible opportunistic exploitation probability, though multi-tenant jail environments relying on ktrace for security auditing face a meaningful auditability risk.
RemediationAI
The FreeBSD Project has released corrective patches: systems running FreeBSD 15.0-RELEASE should update to patch level 12 or later, and systems running FreeBSD 15.1-RELEASE should update to patch level 2 or later, as documented in FreeBSD-SA-26:53.ktrace.asc at https://security.freebsd.org/advisories/FreeBSD-SA-26:53.ktrace.asc. For environments that cannot apply the patch immediately, the most effective compensating control is to audit and restrict which jail users hold debug (ptrace) permissions over other processes, reducing the set of users capable of interacting with jailed root's trace configuration; the trade-off is that this may impair legitimate in-jail debugging workflows. Organizations that depend on ktrace output for compliance or forensic audit trails should treat any tracing gaps on affected systems as potentially tampered and supplement with host-level auditing (e.g., Audit daemon on the host) until patching is complete.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
FreeBSD jails provide OS-level virtualization enforced by the kernel's privilege-check framework, where privilege constants such as PRIV_KTRACE gate sensitive operations even for root inside a jail. The ktrace(2) subsystem records kernel-level system call and event traces for diagnostic and auditing purposes; its privilege model depends on correct evaluation of PRIV_KTRACE to mark sessions initiated by root as privileged and therefore unmodifiable by unprivileged peers. CWE-273 (Improper Check for Dropped Privileges) captures the root cause precisely: an inadvertent code regression caused PRIV_KTRACE to always be denied within jail context, dropping a privilege that jailed root should legitimately hold. The result is that ktrace sessions created by jailed root behave as if initiated by an unprivileged user, allowing any jail user who can debug the target process - via ptrace or equivalent - to overwrite or clear the tracing flags. Affected CPE is cpe:2.3:a:freebsd:freebsd covering FreeBSD 15.0-RELEASE before p12 and 15.1-RELEASE before p2.
Know when Freebsd gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Network vector retained as jail access is plausible via SSH; A:L rather than A:H because impact is limited to disabling tracing within one jail, not broader system availability.
Primary rating from Vendor (freebsd).
CVSS VectorVendor: freebsd
Lifecycle Timeline
3DescriptionCVE.org
As an inadvertent side effect of an unrelated code change, PRIV_KTRACE was always denied to a jailed root user. Tracing configured by a jailed root user was therefore not flagged as privileged.
An unprivileged user in a jail that has permission to debug the target process can modify the jailed root user's ktrace(2) flags, or disable tracing outright. A jailed root user therefore cannot reliably trace unprivileged processes.
Executive ViewAI
FreeBSD 15.x systems with multi-tenant jail configurations are vulnerable to audit logging bypass, where untrusted tenant accounts can disable the root user's security event logging. Organizations relying on kernel-level audit controls face compliance and forensic investigation risks, particularly in production environments with regulatory reporting requirements.
No vendor-released patch identified at time of analysis. Interim mitigations include: (1) restrict debug system capabilities to administratively trusted jail users only; (2) implement complementary centralized or network-based audit logging independent of in-jail kernel tracing; (3) physically or logically segregate untrusted workloads from audit-critical jails; (4) enable administrative alerts on audit configuration changes.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
The x86-64 kernel system-call functionality in Xen 4.1.2 and earlier, as used in Citrix XenServer 6.0.2 and earlier and
The rtsol(8) and rtsold(8) programs do not validate the domain search list options provided in router advertisement mess
Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due
The RFC 5011 implementation in rdata.c in ISC BIND 9.7.x and 9.8.x before 9.8.5-P2, 9.8.6b1, 9.9.x before 9.9.3-P2, and
Remote code execution in OpenSSH's sshd server (regression of CVE-2006-5051) allows unauthenticated remote attackers to
An issue was discovered in OpenSSH 7.9. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no
The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remot
The vm_map_lookup function in sys/vm/vm_map.c in the mmap implementation in the kernel in FreeBSD 9.0 through 9.1-RELEAS
An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. Rated med
Integer overflow in the _gd2GetHeader function in gd_gd2.c in the GD Graphics Library (aka libgd) before 2.2.3, as used
The Stream Control Transmission Protocol (SCTP) module in FreeBSD 9.3 before p33, 10.1 before p26, and 10.2 before p9, w
In FreeBSD 12.1-STABLE before r359565, 12.1-RELEASE before p7, 11.4-STABLE before r362975, 11.4-RELEASE before p1, and 1
EUVD-2026-62340
GHSA-5q67-rff6-c784
NVD
CVE.org
EPSS
VulDB
Exploit-DB