# CVE-2026-86443: Cleartext Storage of Sensitive Information Vulnerability

> Local attackers can retrieve cleartext credentials from the DuoxMe Android app to impersonate user accounts.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **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-w5f7-4jpr-ffh9

## What is CVE-2026-86443?

CVE-2026-86443 is a medium-severity vulnerability in Fermax Electronica S.A.U. DuoxMe, 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

Cleartext storage of sensitive information in the DuoxMe application for Android, in versions prior to 4.3.4, allows an attacker with local access to the device to retrieve the credentials stored by the application and impersonate the user account.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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


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

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

## Is CVE-2026-86443 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86443 is a medium-severity vulnerability in Fermax Electronica S.A.U. DuoxMe, 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-86443 in the wild and no public exploit code.

Affected product: Fermax Electronica S.A.U. DuoxMe. 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-86443/ (Markdown: https://insights.sbomify.com/CVE-2026-86443/index.md)
```

## Sources

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

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