Quick answers
- Is CVE-2026-25826 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-25826 being exploited in the wild.
- How severe is CVE-2026-25826?
- Medium severity, with a CVSS score of 4.9, published 15 September 2026.
- Which products and versions are affected?
- Keyfactor SignServer before 7.6.0.
- Is there a fix for CVE-2026-25826?
- A patch was published on 2026: Fixed in SignServer 7.6.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-25826 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-25826?
- 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
The vulnerability is an information disclosure flaw in the PKCS11CryptoToken component of SignServer. When the ATTRIBUTESFILE attribute is set to a readable file that is not a valid PKCS11 attributes file, an error is thrown that logs the full contents of the file to the application server log. The attack requires two preconditions: SignServer admin access (to configure the token) and ability to read application server logs (feasible if remote syslog is configured). An attacker cannot directly trigger file reads but must rely on administrator misconfiguration or social engineering. The vulnerability was fixed in SignServer 7.6.0 and later versions.
Affected products
- Keyfactor SignServer before 7.6.0
Timeline
- 2026-09-15: disclosed: CVE-2026-25826 published
- 2026: patched: Fixed in SignServer 7.6.0