# CVE-2026-41051: csync2 uses insecure temporary directories when compiled with C99 or later

> Attackers can exploit a race condition in temporary directory handling to escalate privileges or modify data in csync2.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 May 2026
- **Updated:** 13 May 2026
- **Also known as:** DEBIAN-CVE-2026-41051, GHSA-7mqw-hr29-pj76, SUSE-SU-2026:2116-1, SUSE-SU-2026:21994-1, SUSE-SU-2026:22041-1, UBUNTU-CVE-2026-41051, openSUSE-SU-2026:10600-1, openSUSE-SU-2026:20900-1

## What is CVE-2026-41051?

CVE-2026-41051 is a medium-severity vulnerability in openSUSE Tumbleweed, published on 13 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

csync2 uses insecure temporary directories when compiled with C99 or later, allowing for TOCTOU style attacks on the temporary directories.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2026-41051?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `csync2` | SUSE:Linux Enterprise High Availability Extension 16.0 | All versions | 2.0+git.1600444747.83b3644-160000.3.1 |
| `csync2` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 2.0+git.1600444747.83b3644-160000.3.1 |
| `csync2` | openSUSE:Tumbleweed | All versions | 2.0+git.1600444747.83b3644-3.1 |

## How do I fix CVE-2026-41051?

Apply the vendor's patch.

## Is CVE-2026-41051 being exploited?

There is no known exploitation of CVE-2026-41051 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41051 and fix it if it is affected.

What it is: CVE-2026-41051 is a medium-severity vulnerability in openSUSE Tumbleweed, published on 13 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-41051 in the wild and no public exploit code.

Affected product: openSUSE Tumbleweed. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41051/ (Markdown: https://insights.sbomify.com/CVE-2026-41051/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41051
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41051
- OSV: https://osv.dev/vulnerability/CVE-2026-41051

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41051/
Summaries are generated and may contain mistakes; the official description above is the record.