Skip to main content
Mallory
UnratedVulnerability

CVE-2026-55869: Stack-based buffer overflow in SRT keying-material control packet handling

Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-55869CWE-121

CVE-2026-55869 is a stack-based buffer overflow in the Secure Reliable Transport (SRT) UDP streaming library. During connection setup or key-refresh operations, a keying-material request (KMREQ) or response (KMRSP) control packet is copied into a fixed-size stack buffer using a packet-supplied length without adequate validation. An oversized control packet can write beyond the buffer boundary, potentially crashing the application using SRT and causing denial of service.

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.

A remote attacker can potentially crash a process using a vulnerable SRT socket, interrupting streaming sessions and making the service unavailable. Although the assigned CVSS v3 vector includes high confidentiality impact, the available technical details establish stack memory corruption and potential denial of service, not a specific information-disclosure or code-execution capability. The encryption-bypass issue addressed alongside this vulnerability is CVE-2026-55868.

Mitigation

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

Until updates are installed, restrict network access to SRT services to trusted networks and peers where operationally feasible. Monitor SRT applications for unexpected crashes and stream interruptions. These measures reduce exposure but do not correct the buffer overflow.

Remediation

Patch, then assume compromise.

Upgrade affected SRT packages to the distribution's fixed versions. Debian 13 trixie fixes the vulnerability in version 1.5.4-1+deb13u1, and Debian 12 bookworm fixes it in version 1.5.1-1+deb12u2. For Ubuntu 20.04, 22.04, 24.04, and 26.04, install the applicable security updates covered by USN-8764-1, using Ubuntu Pro ESM Apps where required. Exact fixed Ubuntu package versions are not available in the supplied information.

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.
FAQ

Frequently asked questions

Is CVE-2026-55869 exploited in the wild?
As of Nov 11, 2026, Mallory has no reports of CVE-2026-55869 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-55869?
As of Nov 11, 2026, Mallory has found no public exploit for CVE-2026-55869.
Is there a patch for CVE-2026-55869?
Upgrade affected SRT packages to the distribution's fixed versions. Debian 13 trixie fixes the vulnerability in version 1.5.4-1+deb13u1, and Debian 12 bookworm fixes it in version 1.5.1-1+deb12u2.
Activity feed

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, 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.