# CVE-2025-9071: Insecure RSA-OAEP implementation with all-zero seed for padding in Oberon PSA Crypto

> Insecure RSA-OAEP implementation using an all-zero seed allows attackers to decrypt guessable messages and identify repeated ciphertexts in Oberon PSA Crypto.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/S:N/RE:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Aug 2025
- **Updated:** 29 Aug 2025
- **Also known as:** GHSA-5h27-5x9j-ffpx

## What is CVE-2025-9071?

CVE-2025-9071 is a low-severity vulnerability in Oberon PSA Crypto, published on 29 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Erroneously using an all-zero seed for RSA-OEAP padding instead of the generated random bytes, in Oberon microsystems AG’s Oberon PSA Crypto library in all versions up to 1.5.1, results in deterministic RSA and thus in a loss of confidentiality for guessable messages, recognition of repeated messages, and loss of security proofs.

Weakness: CWE-780 (Use of RSA Algorithm without OAEP)

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


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

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

## Is CVE-2025-9071 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9071 is a low-severity vulnerability in Oberon PSA Crypto, published on 29 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-9071 in the wild and no public exploit code.

Affected product: Oberon PSA Crypto. 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-9071/ (Markdown: https://insights.sbomify.com/CVE-2025-9071/index.md)
```

## Sources

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

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