# CVE-2026-120336: VStarcam O-KAM Client DevDll_925.dll FUN_10003EA0 stack-based overflow


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-5m28-h7xq-m9g4

## What is CVE-2026-120336?

CVE-2026-120336 is a medium-severity vulnerability in VStarcam O-KAM Client, published on 2 Nov 2026. 

### Official description

A vulnerability was found in VStarcam O-KAM Client 1.3.3.32. Affected by this vulnerability is the function FUN_10003EA0 in the library DevDll_925.dll. The manipulation results in stack-based buffer overflow. It is possible to launch the attack remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-120336 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120336 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120336 is a medium-severity vulnerability in VStarcam O-KAM Client, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120336 exists.

Affected product: VStarcam O-KAM Client. 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-120336/ (Markdown: https://insights.sbomify.com/CVE-2026-120336/index.md)
```

## Sources

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

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