# CVE-2026-25827: Information disclosure in n/a

> An admin user can exploit unrestricted path properties to confirm the existence of arbitrary files on the server, leading to information disclosure.

- **Severity:** Low 2.3 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-3fm2-px7p-2749

## What is CVE-2026-25827?

CVE-2026-25827 is a low-severity vulnerability in n/a, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-538 (Insertion of Sensitive Information into Externally-Accessible File or Directory)

## Which versions are affected by CVE-2026-25827?


## How do I fix CVE-2026-25827?

No fix has been published for CVE-2026-25827 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-25827 being exploited?

There is no known exploitation of CVE-2026-25827 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25827 and fix it if it is affected.

What it is: CVE-2026-25827 is a low-severity vulnerability in n/a, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25827 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25827/ (Markdown: https://insights.sbomify.com/CVE-2026-25827/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25827
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25827
- OSV: https://osv.dev/vulnerability/CVE-2026-25827

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25827/
Summaries are generated and may contain mistakes; the official description above is the record.