CVE-2026-57895
Local privilege escalation via insecure default permissions in Pupsman <3.9.0
Is CVE-2026-57895 being exploited?
Not confirmed. CVE-2026-57895 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.16% probability of exploitation in the next 30 days.
How severe is CVE-2026-57895?
CVE-2026-57895 is rated High with a CVSS score of 8.5. 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-57895?
Yes. A fix has been recorded for CVE-2026-57895. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-57895 affect?
CVE-2026-57895 affects Pupsman < 3.9.0 (Windows), Windows servers/workstations with Pupsman installed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-57895?
Upgrade to Pupsman 3.9.0 immediately and restrict installation-folder ACLs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can place a malicious executable in install folder and achieve arbitrary code execution as SYSTEM.
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.