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

> Attackers can retrieve sensitive product properties from other clients, potentially exposing secrets like domain join passwords and enabling privilege escalation.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2025
- **Updated:** 9 Sep 2025
- **Also known as:** GHSA-rwhj-jgcw-rhrm

## What is CVE-2025-22956?

CVE-2025-22956 is a critical vulnerability in n/a, published on 8 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OPSI before 4.3 allows any client to retrieve any ProductPropertyState, including those of other clients. This can lead to privilege escalation if any ProductPropertyState contains a secret only intended to be accessible by a subset of clients. One example of this is a domain join account password for the windomain package.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2025-22956 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-22956 is a critical vulnerability in n/a, published on 8 Sep 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-22956 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-22956/ (Markdown: https://insights.sbomify.com/CVE-2025-22956/index.md)
```

## Sources

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

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