Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2022-26259: RTSP stack-based buffer overflow in Xiongmai DVR devices

Published Mar 28, 2022 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS2.4%84th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Xiongmaitech
IdentifiersCVE-2022-26259CWE-121

CVE-2022-26259 is an unauthenticated stack-based buffer overflow in the RTSP parsing logic of multiple Xiongmai DVR devices, including NBD80X16S-KL, NBD80X09S-KL, NBD80X08S-KL, NBD80X09RA-KL, AHB80X04R-MH, AHB80X04R-MH-V2, AHB80X04-R-MH-V3, AHB80N16T-GS, AHB80N32F4-LME, and NBD90S0VT-QW. The flaw is reachable over the network via the RTSP service on TCP port 554 by sending a crafted RTSP request. The provided content characterizes the issue as a stack-based overflow in RTSP parsing and notes that exploitation constraints include payload restrictions such as no null bytes and no space characters. Although the short description mentions denial of service, the supporting content states VulnCheck successfully developed remote code execution against affected Xiongmai test devices, indicating the overflow is exploitable beyond a crash condition on at least some firmware variants.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can crash the RTSP service or the device, causing denial of service. Based on the supporting content, the vulnerability can also be leveraged for remote code execution on affected devices, which would allow an attacker to execute arbitrary code in the device context without authentication. In practical terms, this can enable full device compromise, botnet enrollment, follow-on access enablement such as starting telnetd, persistence or staging of additional payloads, and use of the device as a pivot or proxy within attacker infrastructure.

Mitigation

If you can’t patch tonight, do this now.

Do not expose the RTSP service on port 554 directly to the internet. Restrict access to trusted management or viewing networks using firewall rules, ACLs, VPN-only access, or segmentation. Disable RTSP if it is not operationally required. Continuously inventory internet-exposed Xiongmai/OEM devices and monitor for unexpected services or signs of compromise. Where patching is delayed or unavailable, isolate the device from untrusted networks and consider compensating controls such as upstream filtering and strict ingress restrictions.

Remediation

Patch, then assume compromise.

Apply vendor-provided firmware updates or security fixes from Xiongmai or the downstream OEM/rebrander for the affected device model. Because the content notes that some rebranded devices may remain exploitable even when not explicitly listed as affected, operators should verify the exact firmware lineage and test whether the RTSP service remains vulnerable after upgrade. If no fixed firmware is available from the vendor or OEM, replace the affected device with a supported model.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
XiongmaitechAhb80n16t-Gs Firmwareoperating_system
XiongmaitechAhb80n32f4-Lme Firmwareoperating_system
XiongmaitechAhb80x04-R-Mh-V3 Firmwareoperating_system
XiongmaitechAhb80x04r-Mh Firmwareoperating_system
XiongmaitechAhb80x04r-Mh-V2 Firmwareoperating_system
XiongmaitechNbd80x08s-Kl Firmwareoperating_system
XiongmaitechNbd80x09ra-Kl Firmwareoperating_system
XiongmaitechNbd80x09s-Kl Firmwareoperating_system
XiongmaitechNbd80x16s-Kl Firmwareoperating_system
XiongmaitechNbd90s0vt-Qw Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2022-26259 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2022-26259 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2022-26259?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2022-26259.
Is there a patch for CVE-2022-26259?
Apply vendor-provided firmware updates or security fixes from Xiongmai or the downstream OEM/rebrander for the affected device model. Because the content notes that some rebranded devices may remain exploitable even when not explicitly listed as affected, operators should verify the exact firmware lineage and test whether the RTSP service remains vulnerable after upgrade.
What products are affected by CVE-2022-26259?
Xiongmaitech Ahb80n16t-Gs Firmware, Xiongmaitech Ahb80n32f4-Lme Firmware, Xiongmaitech Ahb80x04r-Mh Firmware, Xiongmaitech Ahb80x04r-Mh-V2 Firmware, Xiongmaitech Ahb80x04-R-Mh-V3 Firmware, and 5 more.
How severe is CVE-2022-26259?
CVE-2022-26259 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 2.4% (84th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.