# CVE-2026-89174: Kingdom Communication Associated｜Smart Video Intercom System - Missing Burte-force Protection

> Unauthenticated attackers can brute-force login attempts to gain access to valid accounts on Kingdom Communication Smart Video Intercom systems.

- **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:** 11 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-4292-rc2p-fghr

## What is CVE-2026-89174?

CVE-2026-89174 is a high-severity authentication bypass vulnerability in Kingdom Communication Associated EH1000B, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Smart Video Intercom System developed by Kingdom Communication Associated has a Missing Brute-force Protection vulnerability. Unauthenticated remote attackers can gain access to valid accounts through a large number of login attempts.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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


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

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

## Is CVE-2026-89174 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89174 is a high-severity authentication bypass vulnerability in Kingdom Communication Associated EH1000B, published on 11 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-89174 in the wild and no public exploit code.

Affected product: Kingdom Communication Associated EH1000B. 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-89174/ (Markdown: https://insights.sbomify.com/CVE-2026-89174/index.md)
```

## Sources

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

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