Service interruption via failed secure-mkstemp detection
Published May 13, 2026 · Updated May 13, 2026
csync2 on openSUSE Tumbleweed before 2.0+git.1600444747.83b3644-3.1 allows local users to interrupt service through a temporary-directory race. The configure.ac secure-mkstemp probe declares main without an explicit return type, so C99-or-later builds reject the probe and omit HAVE_SECURE_MKSTEMP, selecting unsafe temporary-directory handling. Exploitation requires low-privileged local access and interaction with a victim csync2 run; the published impact is availability only.
Summary
What happened
csync2 on openSUSE Tumbleweed before 2.0+git.1600444747.83b3644-3.1 allows local users to interrupt service through a temporary-directory race. The configure.ac secure-mkstemp probe declares main without an explicit return type, so C99-or-later builds reject the probe and omit HAVE_SECURE_MKSTEMP, selecting unsafe temporary-directory handling. Exploitation requires low-privileged local access and interaction with a victim csync2 run; the published impact is availability only.
The record
- CVE
- CVE-2026-41051
- Published
- May 13, 2026
- Updated
- May 13, 2026
- Vendor
- OpenSUSE
- Product
- openSUSE Tumbleweed
- Classifications
- CWE-367, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 2026CVE publishedPublication date reported by the CVE source.
- May 13, 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=? <2.0+git.1600444747.83b3644-3.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