Quick answers
- Is CVE-2025-41259 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-41259 being exploited in the wild.
- How severe is CVE-2025-41259?
- Informational severity, with a CVSS score of 7.3, published 3 June 2026.
- Which products and versions are affected?
- Sbabic SWUpdate before 2026.05.
- Is there a fix for CVE-2025-41259?
- A patch was published on 2026-05-29: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-41259 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2025-41259?
- Check whether you run Sbabic SWUpdate at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Time-of-Check Time-of-Use (TOCTOU) race condition exists in SWUpdate's handling of temporary directories during the update extraction process. SWUpdate extracts signed CPIO archives to a temporary directory (typically /tmp) and performs integrity checks on individual files. Because /tmp often has the sticky bit set, a local unprivileged attacker can pre-create a 'scripts' directory or manipulate the file structure between the time SWUpdate verifies the signature/integrity and the time it executes the contained scripts. This allows the attacker to bypass signature verification and execute arbitrary code with root privileges. The vulnerability is addressed in version 2026.05 by ensuring proper directory validation and cleanup.
Affected products
- sbabic SWUpdate before 2026.05
Timeline
- 2026-06-03: advisory: NVD publication date
- 2026-05-29: patched: Fix committed to repository