CVE-2026-56437
DLL search path flaw in Pupsman installer allows SYSTEM code execution.
Is CVE-2026-56437 being exploited?
Not confirmed. CVE-2026-56437 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.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-56437?
CVE-2026-56437 is rated High with a CVSS score of 8.4. 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-56437?
Yes. A fix has been recorded for CVE-2026-56437. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-56437 affect?
CVE-2026-56437 affects Pupsman < 3.9.0 installers on Windows, Windows hosts where installer is executed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-56437?
Upgrade Pupsman to 3.9.0+, avoid running untrusted installers, scan installer directories for unknown DLLs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Placing a crafted DLL beside the installer lets an attacker execute arbitrary code as SYSTEM on Windows.
Immediate action required
- affectedprior to 3.9.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.