# CVE-2026-123787: nexmoe VidBee Local HTTP Service local-api.ts information disclosure


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-f6px-p9gh-qvmh

## What is CVE-2026-123787?

CVE-2026-123787 is a medium-severity vulnerability in nexmoe VidBee, published on 6 Nov 2026. 

### Official description

A weakness has been identified in nexmoe VidBee up to 1.3.13/2.0.2. The affected element is an unknown function of the file apps/desktop/src/main/local-api.ts of the component Local HTTP Service. Executing a manipulation can lead to information disclosure. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 2.2.0 is sufficient to fix this issue. This patch is called 141b8d39c1c11da4589264f814cee077df81e7f6. It is suggested to upgrade the affected component.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-123787 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123787 is a medium-severity vulnerability in nexmoe VidBee, published on 6 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123787 exists.

Affected product: nexmoe VidBee. 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-123787/ (Markdown: https://insights.sbomify.com/CVE-2026-123787/index.md)
```

## Sources

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

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