CVE-2026-25827
LOWDescription
An issue was discovered in Keyfactor SignServer before 7.6.0. A number of properties were identified to not have any restrictions to 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. Three specific properties were identified: The property ATTRIBUTESFILE in PKCS11CryotoToken can be set to a readable but not an accepted (i.e., recognized with attributes) file. In this case an error is thrown, confirming the existence of the file. The property KEYSTOREPATH in KeyStoreCryptoToken can be set to a non-existing file that will return an error confirming to the client side that the file does not exist. The property TRUSTSTOREPATH in RenewalWorker can be set to any path (without any restrictions) by an admin user. In the case that the provided path points to an existing file, readable by the user running the application server, but is not a recognized PEM format, it returns this as an error to the client side, confirming the existences of the file.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 2% of all known CVEs.
References
Related Vulnerabilities
Other CWE-538 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-51977 | Medium | 5.3 | 73% | - | - |
| CVE-2019-6851 | High | 7.5 | 30% | - | - |
| CVE-2017-9947 | Medium | 5.3 | 7.3% | - | Fix |
| CVE-2018-11798 | Medium | 6.5 | 4.9% | - | Fix |
| CVE-2017-16770 | Medium | 6.5 | 1.8% | - | Fix |
| CVE-2018-10590 | High | 7.5 | 1.7% | - | Fix |
Common questions
How do I fix CVE-2026-25827?
No published fix for CVE-2026-25827 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-25827 being actively exploited?
Not that we know of. CVE-2026-25827 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.12% is the estimated probability that it will be exploited in the next 30 days. That is higher than 2% of all scored CVEs.
How severe is CVE-2026-25827?
CVE-2026-25827 has a CVSS v3 base score of 2.3, rated low. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-25827
Markdown
[](https://tridentstack.com/cve/CVE-2026-25827)HTML
<a href="https://tridentstack.com/cve/CVE-2026-25827"><img src="https://tridentstack.com/cve/badge/CVE-2026-25827.svg" alt="CVE-2026-25827"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-16.