{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-26928 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-26928 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-26928 is a high-severity code injection vulnerability in Krajowa Izba Rozliczeniowa SzafirHost, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-26928 and fix it if it is affected.\n\nWhat it is: CVE-2026-26928 is a high-severity code injection vulnerability in Krajowa Izba Rozliczeniowa SzafirHost, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-26928 in the wild and no public exploit code.\n\nAffected product: Krajowa Izba Rozliczeniowa SzafirHost. 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-26928/ (Markdown: https://insights.sbomify.com/CVE-2026-26928/index.md)","id":"CVE-2026-26928","markdown":"https://insights.sbomify.com/CVE-2026-26928/index.md","name":"CVE-2026-26928","record":{"aliases":["GHSA-cg6j-gw4m-cw76"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"SzafirHost desktop app","requires_auth":"none","summary":"Attackers can execute arbitrary code by providing malicious dynamic libraries that bypass signature verification in SzafirHost.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"}],"description":"SzafirHost downloads necessary files in the context of the initiating web page. When called, SzafirHost updates its dynamic library. JAR files are correctly verified based on a list of trusted file hashes, and if a file was not on that list, it was checked to see if it had been digitally signed by the vendor. The application doesn't verify hash or vendor's digital signature of uploaded DLL, SO, JNILIB or DYLIB file. The attacker can provide malicious file which will be saved in users /temp folder and executed by the application.\n\nThis issue was fixed in version 1.1.0.","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":"Lack of Dynamic Library Validation in SzafirHost","id":"CVE-2026-26928","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":"Apache Airflow: Wildcard DagVersion Listing Bypasses Per‑DAG RBAC and Leaks Metadata","id":"CVE-2026-26929"},"packages":[],"prev":{"headline":"URL (HTTP Origin) call location spoofing in Szafir SDK Web","id":"CVE-2026-26927"},"products":["SzafirHost"],"published":"2026-04-02","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-02","vendors":["Krajowa Izba Rozliczeniowa"]},"summary":"Attackers can execute arbitrary code by providing malicious dynamic libraries that bypass signature verification in SzafirHost.","url":"https://insights.sbomify.com/CVE-2026-26928/"}