CVE-2026-25827: Software Security Vulnerability Vulnerability

LOW
Advisory Identifier: GHSA-3fm2-px7p-2749
Share
CVSS 2.3
CWE-538
Published
Advisory Summary

CVE-2026-25827 is a LOW (CVSS 2.3) security vulnerability vulnerability (CWE-538: Insertion of Sensitive Information into Externally-Accessible File or Directory) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-25827 at a Glance

CVE Identifier CVE-2026-25827
GHSA Identifier GHSA-3fm2-px7p-2749
Severity LOW
CVSS v3.1 Base Score 2.3
CWE Classification CWE-538: Insertion of Sensitive Information into Externally-Accessible File or Directory
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 2.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-25827

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-25827, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-538: Insertion of Sensitive Information into Externally-Accessible File or Directory, where the product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-25827 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-25827
keyfactor.com WEB
https://keyfactor.com
support.keyfactor.com/hc/en-us/articles/4... WEB
https://support.keyfactor.com/hc/en-us/articles/46345356843291-SignServer-CVE-2026-25827-Local-File-Enumeration

Frequently Asked Questions

What is CVE-2026-25827?
CVE-2026-25827 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-538: Insertion of Sensitive Information into Externally-Accessible File or Directory.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-25827?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-25827?
CVE-2026-25827 has a CVSS v3.1 base score of 2.3 (LOW) with vector string CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2026-25827?
CVE-2026-25827 is classified under CWE-538: Insertion of Sensitive Information into Externally-Accessible File or Directory (The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information.).
How can I check Maven dependencies for CVE-2026-25827?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-3fm2-px7p-2749",
  "modified" : "2026-09-16T18:31:36Z",
  "published" : "2026-09-15T15:32:11Z",
  "aliases" : [ "CVE-2026-25827" ],
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-25827"
  }, {
    "type" : "WEB",
    "url" : "https://keyfactor.com"
  }, {
    "type" : "WEB",
    "url" : "https://support.keyfactor.com/hc/en-us/articles/46345356843291-SignServer-CVE-2026-25827-Local-File-Enumeration"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-538" ],
    "severity" : "LOW",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-15T15:17:14Z"
  }
}