Persistent root execution via GPG filename option
Published Mar 9, 2026 · Updated Mar 9, 2026
Improper signature verification in MBS UBR firmware before 6.0.1.0 allows remote authenticated users to execute code as root. The wwwupdate.cgi handler passes a sanitized, attacker-controlled filename to GPG as an option; a name such as '-h f.upd' forces a zero status and preserves an unsigned update. An administrator credential or stolen administrator session token is required, and a malicious update grants persistent root access and arbitrary system-file modification.
Summary
What happened
Improper signature verification in MBS UBR firmware before 6.0.1.0 allows remote authenticated users to execute code as root. The wwwupdate.cgi handler passes a sanitized, attacker-controlled filename to GPG as an option; a name such as '-h f.upd' forces a zero status and preserves an unsigned update. An administrator credential or stolen administrator session token is required, and a malicious update grants persistent root access and arbitrary system-file modification.
The record
- CVE
- CVE-2025-41767
- Published
- Mar 9, 2026
- Updated
- Mar 9, 2026
- Vendor
- MBS GmbH
- Product
- UBR | LON
- Classifications
- CWE-347, T1068
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Mar 9, 2026CVE publishedPublication date reported by the CVE source.
- Mar 9, 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=0.0.0 <6.0.1.0
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