# CVE-2025-7395: Domain Name Validation Bypass with Apple Native Certificate Validation

> Attackers can bypass domain name validation in wolfSSL when using Apple native certificate validation, allowing acceptance of any trusted CA certificate.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/AU:Y/V:D/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Jul 2025
- **Updated:** 21 Jul 2025
- **Also known as:** GHSA-g6x8-5jj7-qqfv, JLSEC-2026-690, UBUNTU-CVE-2025-7395

## What is CVE-2025-7395?

CVE-2025-7395 is a critical vulnerability in wolfSSL, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A certificate verification error in wolfSSL when building with the WOLFSSL_SYS_CA_CERTS and WOLFSSL_APPLE_NATIVE_CERT_VALIDATION options results in the wolfSSL
 client failing to properly verify the server certificate's domain name,
 allowing any certificate issued by a trusted CA to be accepted regardless of the hostname.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

Apply the vendor's patch.

## Is CVE-2025-7395 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7395 is a critical vulnerability in wolfSSL, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-7395 in the wild and no public exploit code.

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

## Sources

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

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