Skip to main content
Mallory
MediumVulnerability

CVE-2026-57916: Arbitrary URI Handling in proCertum SmartSign CPS Processing

Published Jul 27, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.6Medium · v4
EPSS0.11%1st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-57916CWE-73 · External Control of File Name or…

CVE-2026-57916 is a vulnerability in Asseco proCertum SmartSign affecting versions prior to 9.4.3.90. The application opens the Certificate Practice Statement (CPS) URI embedded in a certificate without validating the URI schema. An attacker can create a certificate containing a CPS URI that references a local executable or an arbitrary web resource, use that certificate to sign a document, and deliver the signed document to a victim. When the victim opens the document in proCertum SmartSign, the application follows the attacker-controlled CPS URI, resulting in execution of the referenced local file or opening of the specified webpage. The issue is classified as CWE-73 due to external control over the resource path or target handled by the application.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to cause proCertum SmartSign to invoke an attacker-controlled CPS target when a victim opens a signed document. Depending on the URI target, this can result in execution of a local executable in the victim context or forced opening of an arbitrary webpage. The vulnerability therefore enables unintended code or program execution behavior and can also be used to drive the victim to attacker-chosen web content, creating opportunities for further compromise, phishing, or follow-on exploitation.

Mitigation

If you can’t patch tonight, do this now.

Until the fixed version can be deployed, reduce exposure by avoiding opening signed documents from untrusted or unverifiable sources in proCertum SmartSign, especially documents signed with certificates not issued by trusted authorities or not previously validated through independent channels. Where operationally feasible, restrict the application's ability to launch external handlers or access untrusted web content through endpoint control policies and application allowlisting.

Remediation

Patch, then assume compromise.

Upgrade proCertum SmartSign to version 9.4.3.90 or later, which fixes the CPS URI handling flaw by addressing the unsafe processing of unvalidated certificate CPS links.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-57916 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-57916 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-57916?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-57916.
Is there a patch for CVE-2026-57916?
Upgrade proCertum SmartSign to version 9.4.3.90 or later, which fixes the CPS URI handling flaw by addressing the unsafe processing of unvalidated certificate CPS links.
How severe is CVE-2026-57916?
CVE-2026-57916 has a CVSS v4 score of 4.6 (Medium) and an EPSS score of 0.11% (1st percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.