Skip to main content
Mallory
UnratedVulnerability

CVE-2026-120211: MIMEDefang PID-file symlink following leading to privileged file overwrite

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

CVE-2026-120211 is a symbolic-link following vulnerability in MIMEDefang PID-file handling. A privileged PID-file write can follow a symbolic link and overwrite its target rather than the intended PID file. The vulnerability was fixed upstream in MIMEDefang 3.7.2; the complete affected-version range and specific vulnerable function are not identified.

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 permits privileged file overwrite, compromising the integrity of files writable by the affected process. Depending on the target, this could corrupt application or system data and disrupt services. Arbitrary code execution, privilege escalation, and confidentiality loss are not independently established by the available technical details.

Mitigation

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

As a defensive precaution, prevent untrusted users and processes from creating or replacing the PID file or modifying its parent directory, and minimize service privileges where operationally supported. These measures are not a confirmed vendor workaround; their effectiveness depends on the PID file location, ownership, and write behavior.

Remediation

Patch, then assume compromise.

Upgrade to MIMEDefang 3.7.2 or a later release containing the fix. Distribution builds incorporating the fix include mimedefang-3.7.3-1.fc43, mimedefang-3.7.3-1.fc44, mimedefang-3.7.3-1.fc45, mimedefang-3.7.3-1.el8, mimedefang-3.7.3-1.el9, mimedefang-3.7.3-1.el10_3, and mimedefang-3.7.3-1.el10_4. These distribution updates were listed as testing or pending testing; validate their current release status before deployment. A separate Debian advisory lists no vendor-supplied fix, so Debian package remediation availability remains distribution-specific.

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-120211 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-120211 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-120211?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-120211.
Is there a patch for CVE-2026-120211?
Upgrade to MIMEDefang 3.7.2 or a later release containing the fix. Distribution builds incorporating the fix include mimedefang-3.7.3-1.fc43, mimedefang-3.7.3-1.fc44, mimedefang-3.7.3-1.fc45, mimedefang-3.7.3-1.el8, mimedefang-3.7.3-1.el9, mimedefang-3.7.3-1.el10_3, and mimedefang-3.7.3-1.el10_4.
Activity feed

Recent activity

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

View more in app →
+4 more in the timeline. Sign up to see them
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.