Skip to main content
VulnerabilityPublished

CVE-2026-123787: nexmoe VidBee · Information Disclosure

Affects nexmoe VidBeeSource CVE Database V5

0
Compare

Public exploit available · CVSS 5.3 Medium · fixed in 2.2.0 : patch nexmoe VidBee as a priority.

Data as of 6 Nov 2026, 21:04 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulDB)CVSS 4.05.3
CNA (VulDB)CVSS 3.14.3
CNA (VulDB)CVSS 3.04.3
CNA (VulDB)CVSS 2.05.0
Patch
Available – fixed in 2.2.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
nexmoeVidBeeAffected
  • 1.3.0 – 2.0.2
17 affected builds
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:nexmoe:vidbee:*:*:*:*:*:*:*:*

AI-suggested

Upgrade nexmoe VidBee to version 2.2.0 or later, which contains the official fix for this vulnerability. Applying this update fully mitigates the information disclosure risk. No other mitigation steps are indicated.

Description

CVE-2026-123787 is an information disclosure vulnerability in nexmoe VidBee affecting versions 1.3.0 through 1.3.13 and 2.0.0 through 2.0.2. The flaw exists in an unknown function within the Local HTTP Service component (apps/desktop/src/main/local-api.ts). An attacker can remotely exploit this weakness to disclose information. Public exploit code is available. Upgrading to version 2.2.0 addresses this issue.

References

Community reviews

Loading reviews…