Loading vulnerability…
CVE-2026-38447 is a weak API key generation vulnerability in osTicket 1.18.3. The application generates API keys using an MD5-based construction that combines partially predictable inputs, including the current Unix timestamp and the client IP address, with a random component. This design reduces the effective entropy of the resulting token and makes the key space materially more searchable than a properly generated cryptographic token. The vulnerable logic is reported in the API key creation path, where MD5 is used in a security-sensitive context and predictable values are incorporated into the key derivation process. Because an attacker can estimate the time of key creation and may know or infer the associated client IP address, the attacker can brute-force candidate values within a feasible window and recover or forge valid API keys more efficiently than intended.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.