Process disruption via attacker-controlled PID file
Published Jul 23, 2025 · Updated Feb 26, 2026
Improper security decision in mailman3 on SUSE openSUSE Tumbleweed before 3.3.10-2.1 allows local users to signal arbitrary processes. The root-run logrotate postrotate script reads a PID from /run/mailman/master.pid, which the mailman account controls, before sending SIGHUP. Control of the mailman service account is required; the signal can reload, disrupt, or terminate a chosen process, depending on its SIGHUP handling.
Summary
What happened
Improper security decision in mailman3 on SUSE openSUSE Tumbleweed before 3.3.10-2.1 allows local users to signal arbitrary processes. The root-run logrotate postrotate script reads a PID from /run/mailman/master.pid, which the mailman account controls, before sending SIGHUP. Control of the mailman service account is required; the signal can reload, disrupt, or terminate a chosen process, depending on its SIGHUP handling.
The record
- CVE
- CVE-2025-53882
- Published
- Jul 23, 2025
- Updated
- Feb 26, 2026
- Vendor
- NeuVector
- Product
- openSUSE Tumbleweed
- Classifications
- CWE-807, T1489
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 23, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=? <3.3.10-2.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo