CVE-2025-47221
MediumCVSS 5.3Exploitation Probability (EPSS)
Low risk19th percentile - higher than 19% of all known CVEs
Summary
An arbitrary file write vulnerability was found in Keyfactor SignServer versions prior to 7.3.2. The ARCHIVETODISK_FILENAME-PATTERN, ARCHIVETODISK_PATH_BASE, and ARCHIVETODISK_PATH_PATTERN properties can be set to any path, including existing files, allowing an admin user to write files in arbitrary directories and potentially overwrite files accessible by the JBoss user.
Risk Assessment
An administrator or privileged user could overwrite critical files on the server, potentially leading to integrity compromise or code execution. The risk affects filesystem integrity and data confidentiality.
Recommendation
Update Keyfactor SignServer to version 7.3.2 or later. Restrict administrative privileges and monitor changes to archive path configuration.
Other vulnerabilities in Keyfactor SignServer
See all- CVE-2026-25827Low
In Keyfactor SignServer before 7.6.0, several properties were identified to have no restrictions on what path they can be set to by an admin user. Setting these properties to specific file paths can reveal information to the client side. This includes ATTRIBUTESFILE in PKCS11CryptoToken, KEYSTOREPATH in KeyStoreCryptoToken, and TRUSTSTOREPATH in RenewalWorker.
- CVE-2026-25826Medium
In Keyfactor SignServer before 7.6.0, the ATTRIBUTESFILE attribute in PKCS11CryptoToken can be set to a readable file but not an accepted file. In this case, an error is thrown which also prints the file content to the application server log. This allows a user with both SignServer admin access and log read access to read files accessible by the local JBoss user.
- CVE-2026-25825Low
In Keyfactor SignServer before 7.6.0, the output file for SignerStatusReportWorker can be set to any path, even one pointing to an existing file. This allows a user with admin access to write files in arbitrary directories and potentially overwrite files accessible by the local JBoss user.
- CVE-2025-26787Medium
An error in the SignServer container startup logic in Keyfactor SignServer versions prior to 7.2 causes the Admin CLI command configuring certificate access to set the "allowany" property on every container restart instead of only on first startup. This resets the configuration to allow any user with a valid trusted client auth certificate to connect.
- CVE-2025-47222Medium
A class name enumeration was found in Keyfactor SignServer versions prior to 7.3.2. Setting any chosen class name to properties requiring a class path causes different errors depending on whether the class exists in the deployment, returning information about loaded classes to the client side.
- CVE-2025-47220Medium
A local file enumeration was found in Keyfactor SignServer versions prior to 7.3.2. The VISIBLE_SIGNATURE_CUSTOM_IMAGE_PATH property in PDFSigner and PAdESSigner can be set by an admin to any path without restrictions; if it points to an existing file readable by the application server user but not a recognized image format, an error is returned to the client confirming the file's existence.
Original NVD description (English source)
An arbitrary file write was found in Keyfactor SignServer versions prior to 7.3.2. The properties ARCHIVETODISK_FILENAME-PATTERN, ARCHIVETODISK_PATH_BASE, ARCHIVETODISK_PATH_PATTERN can be set to any path, even ones that will point to files that already exist. This vulnerability gives a user with admin access the possibility to write files in arbitrary directories in the server file system and potentially overwrite files accessible by the local user JBoss.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS