# CVE-2025-42904: Information Disclosure vulnerability in Application Server ABAP

> An authenticated attacker can read unmasked values in ABAP Lists, leading to unauthorized data disclosure and high confidentiality impact.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 Dec 2025
- **Updated:** 9 Dec 2025
- **Also known as:** GHSA-9rr5-8349-j433

## What is CVE-2025-42904?

CVE-2025-42904 is a medium-severity vulnerability in SAP_SE Application Server ABAP, published on 9 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Due to an Information Disclosure vulnerability in Application Server ABAP, an authenticated attacker could read unmasked values displayed in ABAP Lists. Successful exploitation could lead to unauthorized disclosure of data, resulting in a high impact on confidentiality without affecting integrity or availability.

Weakness: CWE-549 (Missing Password Field Masking)

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


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

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

## Is CVE-2025-42904 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42904 is a medium-severity vulnerability in SAP_SE Application Server ABAP, published on 9 Dec 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-42904 in the wild and no public exploit code.

Affected product: SAP_SE Application Server ABAP. 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-42904/ (Markdown: https://insights.sbomify.com/CVE-2025-42904/index.md)
```

## Sources

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

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