# CVE-2026-81321: CareCam CM2507 Cleartext Storage of Sensitive Information

> Attackers with filesystem access can recover cleartext wireless credentials from CareCam IP cameras, exposing network security details.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-qh37-vv9h-6h8f

## What is CVE-2026-81321?

CVE-2026-81321 is a critical vulnerability in CareCam HMT.CM2507 Firmware, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CM2507 IP cameras store configured wireless network credentials in cleartext within the device filesystem. An attacker who obtains filesystem access through physical access, a debugging interface, or another vulnerability could recover the configured network identifier and pre-shared key.

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

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


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

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

## Is CVE-2026-81321 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81321 is a critical vulnerability in CareCam HMT.CM2507 Firmware, published on 18 Sep 2026. 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-2026-81321 in the wild and no public exploit code.

Affected product: CareCam HMT.CM2507 Firmware. 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-81321/ (Markdown: https://insights.sbomify.com/CVE-2026-81321/index.md)
```

## Sources

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

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