Vulnerability in Keyfactor SignServer (CVE-2026-25825)
Summary
Vulnerability in Keyfactor SignServer (CVE-2026-25825). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the 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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-25825 has been found in Keyfactor SignServer.
Risk of unauthorized operations or information disclosure. CVSS score: 2.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Keyfactor SignServer CVE-2026-25825" on the vendor's site.
CVE-2026-25825 (Keyfactor SignServer) — CWE-706 / CVSS v3 2.7
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-706) exists in Keyfactor SignServer.
Check the vendor advisory for the affected versions of Keyfactor SignServer.
Severity: Low (CVSS 2.7/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Keyfactor SignServer を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web keyfactor.com
- web support.keyfactor.com
- web nvd.nist.gov
- web github.com