CVE-2026-41447
Local DLL hijack in FirmaCheck (<1.3.16) allows code execution at startup.
Is CVE-2026-41447 being exploited?
Not confirmed. CVE-2026-41447 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.11% probability of exploitation in the next 30 days.
How severe is CVE-2026-41447?
CVE-2026-41447 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-41447?
Yes. A fix has been recorded for CVE-2026-41447. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41447 affect?
CVE-2026-41447 affects FirmaCheck for Windows < 1.3.16, Windows hosts with FirmaCheck installed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41447?
Upgrade to FirmaCheck 1.3.16+, restrict write permissions to Common Files\SSL\
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can achieve arbitrary code execution at FirmaCheck startup by placing a crafted openssl.cnf that loads an attacker DLL.
Immediate action required
- affected< 1.3.16
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.