CVE-2025-47220: signserver · n/a
Affects signserverSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 7.3.2 when convenient.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 7.3.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade com.keyfactor/signserver to 7.3.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavencom.keyfactor/signserverpkg:maven/com.keyfactor/signserverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-47220, European organizations should take the following specific actions: 1) Upgrade Keyfactor SignServer to version 7.3.2 or later, where the vulnerability is addressed. If an upgrade is not immediately possible, 2) restrict administrative access to the SignServer environment to only trusted personnel and enforce strong authentication and authorization controls to prevent unauthorized changes to the VISIBLE_SIGNATURE_CUSTOM_IMAGE_PATH property. 3) Implement monitoring and alerting for changes to configuration properties related to signature images to detect suspicious activity. 4) Conduct regular audits of file permissions and server user privileges to ensure that the application server user has minimal necessary access, limiting exposure of sensitive files. 5) Employ network segmentation and isolation for the SignServer infrastructure to reduce the attack surface. 6) Engage with Keyfactor support or security advisories to obtain any available patches or workarounds. 7) Educate administrators about the risks of improper configuration and the importance of validating file paths used in signature customization. These measures collectively reduce the risk of exploitation and limit the potential impact of the vulnerability.
Description
A local file enumeration was found in Keyfactor SignServer versions prior to 7.3.2 .The property VISIBLE_SIGNATURE_CUSTOM_IMAGE_PATH, which exists in the PDFSigner and the PAdESSigner, can be set to any path without any restrictions by an admin user. In the case that the provided path points to an existing file, readable by the user running the application server, but is not a recognized image format, it will return this as an error to the clientside, confirming the existences of the file.