CVE-2026-58086: As an inadvertent side effect of an unrelated code change, PRIV_KTRACE was always denied to a jailed
Source GCVE Database
Not known to be exploited · CVSS 8.1 High.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
AI-suggested
Until a fix is available, administrators should be aware of the limitation and consider restricting debugging permissions within jails to trusted users only to mitigate the risk of interference with tracing operations.
Description
CVE-2026-58086 is a vulnerability where the PRIV_KTRACE privilege is always denied to a jailed root user due to an unrelated code change. This causes tracing configured by a jailed root user to not be flagged as privileged. As a result, an unprivileged user within the same jail who has permission to debug a target process can alter or disable the jailed root user's tracing flags, preventing reliable tracing of unprivileged processes by the jailed root user.