# CVE-2026-85544: Hardcoded credentials in DS-KD8003

> Attackers can forge legitimate main cards using immutable factory values to gain permission to issue cards on Hikvision intercom devices.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A: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:** 10 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-xp4g-cgjh-m8f2

## What is CVE-2026-85544?

CVE-2026-85544 is a medium-severity vulnerability in Hikvision DS-KD8003, published on 10 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Some Hikvision intercom products utilize an immutable factory value which should be obtained from local network or physical interaction with the device within their main card, which may allow attackers to forge a legitimate main card, thereby gaining the permission to issue cards.

Weakness: CWE-1310 (Missing Ability to Patch ROM Code), CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2026-85544 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85544 is a medium-severity vulnerability in Hikvision DS-KD8003, published on 10 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-85544 in the wild and no public exploit code.

Affected product: Hikvision DS-KD8003. 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-85544/ (Markdown: https://insights.sbomify.com/CVE-2026-85544/index.md)
```

## Sources

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

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