{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-41447 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-41447 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-41447 is a high-severity code injection vulnerability in Zucchetti S.p.a. FirmaCheck, published on 3 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41447 and fix it if it is affected.\n\nWhat it is: CVE-2026-41447 is a high-severity code injection vulnerability in Zucchetti S.p.a. FirmaCheck, published on 3 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-41447 in the wild and no public exploit code.\n\nAffected product: Zucchetti S.p.a. FirmaCheck. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-41447/ (Markdown: https://insights.sbomify.com/CVE-2026-41447/index.md)","id":"CVE-2026-41447","markdown":"https://insights.sbomify.com/CVE-2026-41447/index.md","name":"CVE-2026-41447","record":{"aliases":["GHSA-rv3c-h5mj-3hjw"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows signing software","requires_auth":"low_privilege","summary":"Local attackers can execute arbitrary code by placing a malicious OpenSSL configuration file in a specific directory, triggering DLL hijacking when the application starts.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"FirmaCheck for Windows before 1.3.16 contains a DLL hijacking vulnerability that allows local attackers to execute arbitrary code by placing a crafted openssl.cnf file in the unvalidated C:\\Program Files (x86)\\Common Files\\SSL\\ directory path. Attackers can write a malicious OpenSSL configuration file referencing an attacker-controlled DLL to achieve code execution at startup process privilege level when FirmaCheck.exe runs automatically at system startup.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"FirmaCheck \u003c 1.3.16 DLL Hijacking via Unvalidated OpenSSL Configuration Path","id":"CVE-2026-41447","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"AdGuard Home Authentication Bypass via Path Traversal in Admin-Token Cookie","id":"CVE-2026-41448"},"packages":[],"prev":{"headline":"WattBox 800 \u0026 820 Series \u003c 2.10.0.0 RCE via Diagnostic Endpoints","id":"CVE-2026-41446"},"products":["FirmaCheck"],"published":"2026-08-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Zucchetti S.p.a."]},"summary":"Local attackers can execute arbitrary code by placing a malicious OpenSSL configuration file in a specific directory, triggering DLL hijacking when the application starts.","url":"https://insights.sbomify.com/CVE-2026-41447/"}