# CVE-2026-85083: CareCam Pro IP Cameras Use of Hard-coded Credentials

> Attackers with physical access can use hard-coded bootloader credentials to modify firmware and compromise the IP camera.

- **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:** 11 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-988q-pfqj-3hc5

## What is CVE-2026-85083?

CVE-2026-85083 is a high-severity vulnerability in CareCam ANJIA AJL33PC0801 Firmware, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The ANJIA AJL33PC0801 IP camera uses a hard-coded credential for bootloader authentication. An attacker with physical access to the device may leverage this weakness to gain privileged bootloader access, allowing unauthorized modification of firmware and system configuration and potentially resulting in complete device compromise.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2026-85083 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85083 is a high-severity vulnerability in CareCam ANJIA AJL33PC0801 Firmware, published on 11 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-85083 in the wild and no public exploit code.

Affected product: CareCam ANJIA AJL33PC0801 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-85083/ (Markdown: https://insights.sbomify.com/CVE-2026-85083/index.md)
```

## Sources

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

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