CVE-2026-38447: osTicket · Insufficient Entropy
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
AI-suggested
Until an official fix is available, users should consider restricting API access through network controls or other compensating controls to reduce exposure. Avoid relying on the current API key generation method for security.
Description
osTicket 1.18.3 generates API keys using a predictable construction based on MD5 hashing. The use of MD5, combined with predictable inputs such as the current timestamp and client IP address, significantly reduces entropy. An attacker can approximate the key generation time and brute-force the key space within a feasible time window.
References
- github.com/osTicket/osTicket/blob/v1.18.3/include/class.api.php (opens in a new tab)
- github.com/osTicket/osTicket/blob/v1.18.3/include/class.misc.php (opens in a new tab)
- github.com/osTicket/osTicket/commit/feccb6a3a90863fd31215ee738b39762177e658c (opens in a new tab)
- github.com/fr3akhacks/cve-disclosures/blob/master/osTicket/CVE-2026-38447.md (opens in a new tab)