Skip to main content
VulnerabilityPublished Updated

CVE-2025-22956: OPSI · Information Exposure

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 4.3 : patch affected systems as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

European organizations should immediately upgrade OPSI to version 4.3 or later where this vulnerability is addressed. If upgrading is not immediately possible, implement strict network segmentation to isolate OPSI clients and servers, limiting access only to trusted devices. Employ strong access controls and monitoring on the OPSI server to detect unusual retrieval of ProductPropertyState data. Review and rotate any sensitive credentials stored in OPSI, especially domain join account passwords, to invalidate potentially exposed secrets. Implement logging and alerting on OPSI API calls to identify unauthorized access attempts. Additionally, consider deploying endpoint detection and response (EDR) solutions to monitor for lateral movement and privilege escalation activities that may result from exploitation. Conduct regular security audits and penetration testing focusing on OPSI deployments to ensure no residual exposure remains. Finally, educate IT staff about this vulnerability and the importance of applying patches promptly.

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.

References

Community reviews

Loading reviews…