CVE-2026-38447
Predictable MD5 API keys in osTicket 1.18.3 enable brute-force API access.
Is CVE-2026-38447 being exploited?
Not confirmed. CVE-2026-38447 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.46% probability of exploitation in the next 30 days.
How severe is CVE-2026-38447?
CVE-2026-38447 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-38447?
Not known from our data. No patch reference has been recorded for CVE-2026-38447, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-38447 affect?
CVE-2026-38447 affects osTicket 1.18.3. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-38447?
Disable API keys, restrict by IP, rotate keys; apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Brute-force API keys to gain unauthorized API access: create/modify tickets, exfiltrate data, or trigger RCE if API permits.
Immediate action required