Quick answers
- Is CVE-2026-25825 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-25825 being exploited in the wild.
- How severe is CVE-2026-25825?
- Low severity, with a CVSS score of 2.7, published 15 September 2026.
- Which products and versions are affected?
- Keyfactor SignServer before 7.6.0.
- Is there a fix for CVE-2026-25825?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-25825 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-25825?
- Check whether you run Keyfactor SignServer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in SignerStatusReportWorker in Keyfactor SignServer versions before 7.6.0, where the output file path for status reports is not properly validated. An authenticated administrator can specify any filesystem path—including paths with directory traversal sequences or absolute paths—to write the report file to arbitrary locations. The vulnerability requires administrator access and could result in overwriting files owned by the JBoss application server process, potentially compromising application integrity or availability. The fix is available in version 7.6.0 and later.
Affected products
- Keyfactor SignServer before 7.6.0
Timeline
- 2026-09-15: disclosed