CVE-2026-25825
UnknownSummary
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.
Risk Assessment
An admin can overwrite critical system or application files, potentially leading to system corruption, unauthorized changes, or compromise.
Recommendation
Upgrade SignServer to 7.6.0 or later, restrict admin privileges, and validate output paths for reports.
Other vulnerabilities in Keyfactor SignServer
See all- CVE-2026-25827Unknown
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-25826Unknown
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.
Original NVD description (English source)
An issue was discovered in Keyfactor SignServer before 7.6.0. The output file to which SignerStatusReportWorker logs the report can be set to any path, even one that points to a file that already exists. This gives a user (with admin access) the possibility to write files in arbitrary directories in the server filesystem and potentially overwrite files accessible by the local user JBoss.