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

> An attacker with admin access and log visibility can read arbitrary files accessible by the JBoss user via error logging in Keyfactor SignServer.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-q7jr-643h-vpc8

## What is CVE-2026-25826?

CVE-2026-25826 is a medium-severity vulnerability in n/a, published on 15 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in Keyfactor SignServer before 7.6.0. The attribute ATTRIBUTESFILE in PKCS11CryptoToken can be set to a readable file but not an accepted file (i.e., recognized with attributes). In this case, an error is thrown which - together with the error - also prints the content of the file to the application server log. This gives a user that has both SignServer admin access and access to read the output of the server log (i.e., if remote syslog shipping is configured), the possibility to read the content of files accessible by the local user JBoss.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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


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

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

## Is CVE-2026-25826 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25826 is a medium-severity vulnerability in n/a, published on 15 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25826 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-25826/ (Markdown: https://insights.sbomify.com/CVE-2026-25826/index.md)
```

## Sources

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

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