Skip to main content
Mallory
UnratedVulnerability

CVE-2026-93403: Stack-based buffer overflow in rsyslog mmpstrucdata

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

CVE-2026-93403 is a stack-based buffer overflow in the mmpstrucdata module of rsyslog versions before 8.2606.0. An unauthenticated network sender can trigger the vulnerability by delivering a crafted RFC 5424 syslog message to an affected instance using the module. Exploitation can terminate rsyslogd, 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.

Successful exploitation can crash rsyslogd and interrupt log collection and processing. Although the vulnerability involves stack memory corruption, arbitrary code execution, information disclosure, and integrity compromise are not established by the available vulnerability-specific information.

Mitigation

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

If upgrading is not immediately possible, disable mmpstrucdata processing of network-supplied messages where operationally feasible. Restrict access to syslog listeners to trusted senders to reduce exposure; this does not eliminate risk from compromised or malicious trusted senders.

Remediation

Patch, then assume compromise.

Upgrade rsyslog to upstream version 8.2606.0 or later, or install a distribution package containing the fix. Debian 12 Bookworm includes the fix in version 8.2302.0-1+deb12u2. For Alpine Linux, the security update recommends version 8.2608.0-r0 or later.

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-93403 exploited in the wild?
As of Nov 11, 2026, Mallory has no reports of CVE-2026-93403 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-93403?
As of Nov 11, 2026, Mallory has found no public exploit for CVE-2026-93403.
Is there a patch for CVE-2026-93403?
Upgrade rsyslog to upstream version 8.2606.0 or later, or install a distribution package containing the fix. Debian 12 Bookworm includes the fix in version 8.2302.0-1+deb12u2.
Activity feed

Recent activity

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