Root command execution through configured ban actions
Published Nov 26, 2025 · Updated Dec 3, 2025
Privilege escalation in Fail2Ban 0.11.2 allows local users with limited sudo access to execute configured operations as root. The report attributes this behavior to fail2ban-client accepting a privileged ban action and later executing that configured action with the daemon's root privileges, without identifying a distinct permission check that is bypassed. Upstream closed the report as incorrect because arbitrary root actions are an intended part of the privilege model; exploitation therefore requires prior permission to configure such an action.
Summary
What happened
Privilege escalation in Fail2Ban 0.11.2 allows local users with limited sudo access to execute configured operations as root. The report attributes this behavior to fail2ban-client accepting a privileged ban action and later executing that configured action with the daemon's root privileges, without identifying a distinct permission check that is bypassed. Upstream closed the report as incorrect because arbitrary root actions are an intended part of the privilege model; exploitation therefore requires prior permission to configure such an action.
The record
- CVE
- CVE-2025-45311
- Published
- Nov 26, 2025
- Updated
- Dec 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-266
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 26, 2025CVE publishedPublication date reported by the CVE source.
- Dec 3, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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