# CVE-2026-86474: Improper Certificate Validation in the Firmware Download vulnerability

> Attackers can intercept firmware updates via man-in-the-middle attacks due to missing TLS validation, potentially installing malicious code on VEO monitors.

- **Severity:** High 7.7 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-p3f8-3247-775c

## What is CVE-2026-86474?

CVE-2026-86474 is a high-severity vulnerability in Fermax Electronica S.A.U. DUOX PLUS monitor firmware (VEO Wi-Fi range), published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The lack of TLS certificate validation when downloading firmware updates in VEO and VEO-XS Wi-Fi monitors, in versions prior to 01.48.001, allows an attacker to perform man-in-the-middle attacks on the update channel.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-86474?


## How do I fix CVE-2026-86474?

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

## Is CVE-2026-86474 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86474 and fix it if it is affected.

What it is: CVE-2026-86474 is a high-severity vulnerability in Fermax Electronica S.A.U. DUOX PLUS monitor firmware (VEO Wi-Fi range), published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86474 in the wild and no public exploit code.

Affected product: Fermax Electronica S.A.U. DUOX PLUS monitor firmware (VEO Wi-Fi range). 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-2026-86474/ (Markdown: https://insights.sbomify.com/CVE-2026-86474/index.md)
```

## Sources

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

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