Secuno
ENNL
Book demo

CVE-2026-38447

9.8 CRITICALEPSS 0.67%
  1. Published3 Aug 2026

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-136399.8
An insufficient entropy vulnerability in login logic in Synology DiskStation Manager…
CVE-2026-905628.1
LangBot before 4.10.11 generates password recovery keys with only 24 bits of entropy…
CVE-2026-718519.0
crypto-js is a JavaScript library of crypto standards. Versions of crypto-js prior to…
CVE-2026-23368.8
A privilege escalation vulnerability in Microchip IStaX allows an authenticated…
CVE-2026-342368.2
Auth0-PHP is a PHP SDK for Auth0 Authentication and Management APIs. From version 8.0.0…
CVE-2025-133998.8
A weakness in the web interface’s application layer encryption in VX800v v1.0 allows an…

Frequently asked

Is CVE-2026-38447 being actively exploited?

CVE-2026-38447 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.67%.

How severe is CVE-2026-38447?

CVE-2026-38447 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.67% probability of exploitation.

How do I fix CVE-2026-38447?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-38447 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.