Skip to main content
CVE-2025-42925VulnerabilityPublished

CVE-2025-42925: SAP NetWeaver AS Java (IIOP Service) · Predictable from Observable State

Affects SAP NetWeaver AS Java (IIOP Service)Source CVE Database V5

0

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 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 2026-10-26.

What to do

AI-suggested

1. Monitor SAP's official security advisories closely for patches or updates addressing CVE-2025-42925 and apply them promptly once available. 2. Implement strict access controls and monitoring on accounts with any level of authentication to the SAP NetWeaver AS Java IIOP service, minimizing the number of users with access and enforcing least privilege principles. 3. Employ enhanced logging and anomaly detection to identify unusual patterns of OID requests or brute force attempts targeting the IIOP service. 4. Consider network segmentation to restrict access to the SAP IIOP service only to trusted hosts and users, reducing exposure to potential attackers. 5. Conduct regular security audits and penetration testing focused on SAP environments to detect exploitation attempts or related weaknesses. 6. Where feasible, configure SAP NetWeaver to increase randomness in identifier generation or apply custom patches/workarounds recommended by SAP support. 7. Educate internal users about the risks of credential compromise and enforce strong authentication mechanisms, such as multi-factor authentication, to reduce the likelihood of low-privilege account compromise.

Description

Due to the lack of randomness in assigning Object Identifiers in the SAP NetWeaver AS JAVA IIOP service, an authenticated attacker with low privileges could predict the identifiers by conducting a brute force search. By leveraging knowledge of several identifiers generated close to the same time, the attacker could determine a desired identifier which could enable them to access limited system information. This poses a low risk to confidentiality without impacting the integrity or availability of the service.

References

Community reviews

Loading reviews…