# CVE-2025-42925: Predictable Object Identifier vulnerability in SAP NetWeaver AS Java (IIOP Service)

> An authenticated attacker can predict Object Identifiers in SAP NetWeaver AS Java IIOP service to access limited system information.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2025
- **Updated:** 9 Sep 2025
- **Also known as:** GHSA-8wc6-6cpf-9jh3

## What is CVE-2025-42925?

CVE-2025-42925 is a medium-severity vulnerability in SAP_SE SAP NetWeaver AS Java (IIOP Service), published on 9 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-341 (Predictable from Observable State)

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


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

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

## Is CVE-2025-42925 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42925 is a medium-severity vulnerability in SAP_SE SAP NetWeaver AS Java (IIOP Service), published on 9 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-42925 in the wild and no public exploit code.

Affected product: SAP_SE SAP NetWeaver AS Java (IIOP Service). 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-42925/ (Markdown: https://insights.sbomify.com/CVE-2025-42925/index.md)
```

## Sources

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

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