# CVE-2026-84398: CareCam CM2507 Empty Password in Configuration File

> Attackers can access privileged management functions and sensitive configuration data on CareCam IP cameras due to an empty password in the ONVIF service.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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-4p3q-h8vm-q7v8

## What is CVE-2026-84398?

CVE-2026-84398 is a high-severity 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 accept an empty password for a privileged account exposed through its ONVIF management service. An attacker with network access to the affected device could access privileged management functions and obtain device, user, media-profile, and stream configuration information.

Weakness: CWE-258 (Empty Password in Configuration File)

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


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

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

## Is CVE-2026-84398 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84398 is a high-severity 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-84398 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-84398/ (Markdown: https://insights.sbomify.com/CVE-2026-84398/index.md)
```

## Sources

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

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