# CVE-2026-81305: CareCam CM2507 Inclusion of Functionality from Untrusted Control Sphere

> Attackers with physical access can execute arbitrary code on CareCam IP cameras by inserting malicious scripts on removable media.

- **Severity:** High 7.0 (`CVSS:4.0/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-fgvx-jgrc-crhg

## What is CVE-2026-81305?

CVE-2026-81305 is a high-severity code injection vulnerability in CareCam HMT.CM2507 Firmware, published on 18 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CM2507 IP cameras automatically execute a predetermined script from removable media without verifying its authenticity or integrity. An attacker with physical access to the device could supply a malicious script and execute arbitrary code in the security context of the affected device.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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


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

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

## Is CVE-2026-81305 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81305 is a high-severity code injection vulnerability in CareCam HMT.CM2507 Firmware, published on 18 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-81305 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-81305/ (Markdown: https://insights.sbomify.com/CVE-2026-81305/index.md)
```

## Sources

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

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