{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-57916 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-57916 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-57916 is a medium-severity path traversal vulnerability in Asseco proCertum SmartSign, published on 27 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-57916 and fix it if it is affected.\n\nWhat it is: CVE-2026-57916 is a medium-severity path traversal vulnerability in Asseco proCertum SmartSign, published on 27 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-57916 in the wild and no public exploit code.\n\nAffected product: Asseco proCertum SmartSign. 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-57916/ (Markdown: https://insights.sbomify.com/CVE-2026-57916/index.md)","id":"CVE-2026-57916","markdown":"https://insights.sbomify.com/CVE-2026-57916/index.md","name":"CVE-2026-57916","record":{"aliases":["GHSA-m7cq-h27p-hwp4"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Digital signature software","requires_auth":"none","summary":"Attackers can execute arbitrary code or open malicious URLs by crafting a certificate with a malicious CPS URI, affecting proCertum SmartSign users.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":4.6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"}],"description":"proCertum SmartSign opens Certificate Practice Statement (CPS) URI without schema validation. An attacker can prepare arbitrary certificate with CPS URI pointing to a local executable file or any URL, sign a document with it, and send it to the victim. When the victim opens the document in the application, the specified file will be executed (or webpage will be opened).\n\nThis issue was fixed in version 9.4.3.90.","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":"Arbitrary Path Execution via CPS URI in proCertum SmartSign","id":"CVE-2026-57916","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Improper Restriction of XML External Entity Reference in proCertum SmartSign","id":"CVE-2026-57917"},"packages":[],"prev":{"headline":"Apache Kerby: Kerberos Pre-Authentication Bypass","id":"CVE-2026-57915"},"products":["proCertum SmartSign"],"published":"2026-07-27","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":"partial"},"state":"PUBLISHED","updated":"2026-07-27","vendors":["Asseco"]},"summary":"Attackers can execute arbitrary code or open malicious URLs by crafting a certificate with a malicious CPS URI, affecting proCertum SmartSign users.","url":"https://insights.sbomify.com/CVE-2026-57916/"}