# CVE-2025-46408: Security feature bypass in n/a

> AVTECH EagleEyes bypasses SSL hostname verification, allowing attackers to intercept traffic via man-in-the-middle attacks.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2025
- **Updated:** 17 Sep 2025
- **Also known as:** GHSA-vmvc-qpg6-jpwh

## What is CVE-2025-46408?

CVE-2025-46408 is a critical vulnerability in n/a, published on 15 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the methods push.lite.avtech.com.AvtechLib.GetHttpsResponse and push.lite.avtech.com.Push_HttpService.getNewHttpClient in AVTECH EagleEyes 2.0.0. The methods set ALLOW_ALL_HOSTNAME_VERIFIER, bypassing domain validation.

Weakness: CWE-297 (Improper Validation of Certificate with Host Mismatch)

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

It affects 1 product.


Products: Avtech Eagleeyes\(lite\).

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

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

## Is CVE-2025-46408 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46408 exists.

Public exploit code:

- Improper Hostname Verification in EagleEyes Lite Android Application (github_poc): https://github.com/shinyColumn/CVE-2025-46408

## Other vulnerabilities in n/a

- [CVE-2025-50944](https://insights.sbomify.com/CVE-2025-50944/): Security feature bypass in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46408 is a critical vulnerability in n/a, published on 15 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46408 exists.

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

## Sources

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

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