Skip to main content
VulnerabilityPublished Updated

CVE-2025-53882: openSUSE Tumbleweed mailman3 · Reliance on Untrusted Inputs in a Security Decision

Affects openSUSE Tumbleweed mailman3Source CVE Database V5

0

Not known to be exploited · CVSS 4.4 Medium : upgrade the openSUSE opensuse/mailman3 package to 3.3.10-2.1 when convenient.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score
4.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.3.10-2.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade the openSUSE opensuse/mailman3 package to 3.3.10-2.1.

Affected software

ProductAffectedFixed in
openSUSEopensuse/mailman3pkg:rpm/opensuse/mailman3Other threatsAffected
  • <3.3.10-2.1
Fixed in
  • 3.3.10-2.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

In the interim, administrators should restrict access to the mailman user account to trusted personnel only and audit local user privileges to minimize the risk of exploitation. Reviewing and hardening logrotate configurations to ensure that signal sending is properly controlled and validated can reduce exposure. Employing process isolation techniques, such as containerization or mandatory access controls (e.g., SELinux, AppArmor), can limit the ability of the mailman user to affect arbitrary processes. Regularly monitoring system logs for unusual SIGHUP signals or process restarts related to mailman3 can help detect attempted exploitation. Additionally, consider disabling or limiting the use of logrotate scripts that allow signal sending if not essential. Implementing robust local user authentication and intrusion detection systems will further reduce the risk of local privilege misuse.

Description

A Reliance on Untrusted Inputs in a Security Decision vulnerability in the logrotate configuration for openSUSE mailman3 package allows the mailman user to sent SIGHUP to arbitrary processes. This issue affects openSUSE Tumbleweed: from ? before 3.3.10-2.1.

References

Community reviews

Loading reviews…