Skip to main content
Mallory

Two High-Severity Buffer Overflow Flaws Disclosed in LinkingVision rapidvms

embedded-device-vulnerabilityinternet-facing-service-vulnerabilityproof-of-concept-release
Updated March 24, 2026 at 07:05 AM2 sources
Share:
Two High-Severity Buffer Overflow Flaws Disclosed in LinkingVision rapidvms

Get Ahead of Threats Like This

Know if you're exposed. Before adversaries strike.

Two high-severity vulnerabilities, CVE-2026-33848 and CVE-2026-33849, were disclosed in LinkingVision rapidvms, both classified as CWE-119 improper restriction of operations within the bounds of a memory buffer. The flaws affect rapidvms versions before PR#96 and carry the same CVSS v3.1 vector, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, indicating network-reachable exploitation with low attack complexity, no required privileges, user interaction, and potential for high impact across confidentiality, integrity, and availability.

Both CVE records point to GitHub pull request #96 in the linkingvision/rapidvms repository as the referenced fix or related remediation. Organizations running vulnerable rapidvms builds should review the changes in that pull request, identify any exposed instances, and prioritize upgrading or patching affected systems because successful exploitation could lead to severe compromise of the video management platform.

Timeline

  1. Mar 24, 2026

    CVE-2026-33848 and CVE-2026-33849 are recorded for rapidvms

    Two high-severity CVEs, CVE-2026-33848 and CVE-2026-33849, were recorded for LinkingVision rapidvms on March 24, 2026. The flaws were classified as CWE-119 buffer overflow issues affecting versions before PR #96, with CVSS 3.1 vectors indicating network reachability, low attack complexity, no required privileges, user interaction required, and high impact on confidentiality, integrity, and availability.

  2. Mar 24, 2026

    LinkingVision fixes rapidvms buffer overflow flaws in PR #96

    A fix for buffer overflow vulnerabilities in LinkingVision rapidvms was made available via GitHub pull request #96. Both later CVE records state the issues affect versions before PR #96, indicating this change remediated the flaws.

See the full picture in Mallory

Mallory subscribers get deeper analysis on every story, including:

Impact Assessment

Who’s affected and how

Technical Details

Deep-dive technical analysis

Response Recommendations

Actionable next steps for your team

Indicators of Compromise

IPs, domains, hashes, and more

AI Threads

Ask questions and take action on every story

Advanced Filters

Filter by topic, classification, timeframe

Scheduled Alerts

Get matching stories delivered automatically

Related Stories

Two Buffer Overflows in OVMS3 Expose Vehicle Monitoring Systems to DoS and RCE

Two Buffer Overflows in OVMS3 Expose Vehicle Monitoring Systems to DoS and RCE

Two high-severity vulnerabilities have been disclosed in Open Vehicle Monitoring System 3 (**OVMS3**) version `3.3.005`, both stemming from improper input validation that can lead to buffer overflows. `CVE-2026-42469` affects `canformat_canswitch.cpp`, where the software fails to properly validate a CANswitch DLC value; a remote attacker can send crafted CANswitch frames to trigger a denial of service and potentially achieve arbitrary code execution. The flaw is tracked as **CWE-121** and carries a CVSS v3.1 vector of `AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H`, indicating network-reachable exploitation with no privileges or user interaction required and a high impact on availability. A second flaw, `CVE-2026-42468`, affects `canformat_pcap.cpp`, where OVMS3 does not correctly validate the `phdr.len` field while parsing PCAP input. An attacker can use crafted PCAP data to cause a denial of service and potentially execute arbitrary code; the updated CVSS v3.1 scoring indicates user interaction is required and that confidentiality, integrity, and availability may all be affected. The CVE records were updated to refine severity details, add **CWE-121** classification, and, for `CVE-2026-42469`, include a public GitHub Gist reference.

Yesterday
LanSpy 2.0.1.159 Local Buffer Overflow Flaws Enable Potential Code Execution

LanSpy 2.0.1.159 Local Buffer Overflow Flaws Enable Potential Code Execution

Two high-severity vulnerabilities, `CVE-2018-25265` and `CVE-2018-25268`, were documented for **LanSpy 2.0.1.159**, affecting the application's scan functionality and exposing users to local buffer overflow attacks. The flaws were classified as `CWE-787` and can let an attacker trigger memory corruption by supplying oversized input in the scan section or scan field, causing application crashes and creating a path to arbitrary code execution. The published details indicate that `CVE-2018-25265` can be exploited through structured exception handling (SEH), including egghunter-based shellcode discovery and controlled jumps, while `CVE-2018-25268` allows instruction pointer overwrite with a payload consisting of 688 bytes of padding followed by 4 bytes of attacker-controlled data. Both entries were assigned high-impact CVSS v3.1 and CVSS v4.0 severity metrics, and the records reference material from **LizardSystems**, **Exploit-DB**, and **VulnCheck**.

1 weeks ago
High-Severity Buffer Bounds Flaw in Portwell Engineering Toolkits Driver (CVE-2026-3437)

High-Severity Buffer Bounds Flaw in Portwell Engineering Toolkits Driver (CVE-2026-3437)

CISA published an ICS advisory for **CVE-2026-3437**, a **high-severity** memory safety issue (*CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer*) affecting **Portwell Engineering Toolkits v4.8.2**. The flaw is in the Portwell Engineering Toolkits **driver** and could allow a **local, authenticated attacker** to **read and write arbitrary memory**, enabling **privilege escalation** or **denial of service**; CISA scored it **CVSS v3.1 8.8 (High)** with a local attack vector and low complexity. The CVE record corroborates the same impact and affected version, and additionally lists a **CVSS v4.0** vector consistent with high impact to confidentiality, integrity, and availability. The vulnerability was reported to CISA by **Jason Huang** of **TXOne Networks** (Cyber Threat & Product Defense Center), and the advisory notes deployment across critical infrastructure environments (including **Energy** and **Critical Manufacturing**) with worldwide exposure.

1 months ago

Get Ahead of Threats Like This

Mallory continuously monitors global threat intelligence and correlates it with your attack surface. Know if you're exposed. Before adversaries strike.