# CVE-2025-42978: Insufficiently Secure Hostname Verification for Outbound TLS Connections in SAP NetWeaver Application Server Java

> Attackers can bypass TLS hostname verification to intercept outbound connections and disclose sensitive information from SAP NetWeaver Application Server Java.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Jul 2025
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-2hqw-mcx8-2828

## What is CVE-2025-42978?

CVE-2025-42978 is a low-severity vulnerability in SAP_SE SAP NetWeaver Application Server Java, published on 8 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The widely used component that establishes outbound TLS connections in SAP NetWeaver Application Server Java does not reliably match the hostname that is used for the connection against the wildcard hostname defined in the received certificate of remote TLS server. This might lead to the outbound connection being established to a possibly malicious remote TLS server and hence disclose information. Integrity and Availability are not impacted.

Weakness: CWE-940 (Improper Verification of Source of a Communication Channel)

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


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

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

## Is CVE-2025-42978 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42978 is a low-severity vulnerability in SAP_SE SAP NetWeaver Application Server Java, published on 8 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-42978 in the wild and no public exploit code.

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

## Sources

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

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