# CVE-2025-47222: Information disclosure in n/a

> Attackers can enumerate loaded class names via error message differences, exposing internal application structure in Keyfactor SignServer.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2025
- **Updated:** 17 Dec 2025
- **Also known as:** GHSA-5wpq-pww3-r4mv

## What is CVE-2025-47222?

CVE-2025-47222 is a medium-severity vulnerability in n/a, published on 13 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A class name enumeration was found in Keyfactor SignServer versions prior to 7.3.2. Setting any chosen class name to any of the properties requiring a class path and the provided class is not expected to return different errors if the class exists in deployment or not. This returns information about the classes loaded in the application or not to the clientside.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-47222?

It affects 1 product.


Products: Keyfactor Signserver.

## How do I fix CVE-2025-47222?

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

## Is CVE-2025-47222 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-47220](https://insights.sbomify.com/CVE-2025-47220/): Information disclosure in n/a (medium 5.3)
- [CVE-2025-47221](https://insights.sbomify.com/CVE-2025-47221/): Path traversal in n/a (medium 5.3)
- [CVE-2025-26787](https://insights.sbomify.com/CVE-2025-26787/): Auth bypass in n/a (medium 4.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-47222 and fix it if it is affected.

What it is: CVE-2025-47222 is a medium-severity vulnerability in n/a, published on 13 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-47222 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-2025-47222/ (Markdown: https://insights.sbomify.com/CVE-2025-47222/index.md)
```

## Sources

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

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