# CVE-2026-88259: CareCam CM2507 Missing Authentication for Critical Function

> Unauthenticated attackers can access live video streams from CareCam IP cameras due to missing authentication on the streaming 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:** 21 Sep 2026
- **Also known as:** GHSA-f9cf-88cq-rm9r

## What is CVE-2026-88259?

CVE-2026-88259 is a high-severity missing authorization 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

CareCam CM2507 IP cameras do not require authentication for access to its network video streaming service. An unauthenticated attacker with network access to the affected device could retrieve live camera video.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-88259 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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