Is CVE-2026-53759 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-53759 being exploited in the wild.

How severe is CVE-2026-53759?

Medium severity, with a CVSS score of 4, published 18 August 2026.

Which products and versions are affected?

linuxfabrik-lib (PyPI) < 4.2.0, ECOSYSTEM:introduced=0,fixed=4.2.0.

Is there a fix for CVE-2026-53759?

Yes. linuxfabrik-lib (PyPI): upgrade to 4.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-53759 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-53759?

Check whether you run linuxfabrik-lib (PyPI) 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.

CVE-2026-53759: Linuxfabrik Monitoring Plugins insecure temporary file creation in linuxfabrik-lib

Q: Is there a fix for CVE-2026-53759?

Yes. linuxfabrik-lib (PyPI): upgrade to 4.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-53759 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-53759?

Check whether you run linuxfabrik-lib (PyPI) 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.

CVE-2026-53759 · Severity: medium · CVSS 4 · Published 2026-08-18

A vulnerability in the Linuxfabrik Monitoring Plugins library allows local attackers to manipulate files on the system. The software creates temporary database files in a predictable location, which can be redirected by a malicious user to overwrite or corrupt other important files. This could lead to a service outage or unauthorized modification of data, especially if the monitoring tools are configured to run with administrative privileges.

Technologies: linuxfabrik-lib (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-53759 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53759 being exploited in the wild.
How severe is CVE-2026-53759?: Medium severity, with a CVSS score of 4, published 18 August 2026.
Which products and versions are affected?: linuxfabrik-lib (PyPI) < 4.2.0, ECOSYSTEM:introduced=0,fixed=4.2.0.
Is there a fix for CVE-2026-53759?: Yes. linuxfabrik-lib (PyPI): upgrade to 4.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53759 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-53759?: Check whether you run linuxfabrik-lib (PyPI) 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.

How to fix

linuxfabrik-lib (PyPI): upgrade to 4.2.0 or later
```
pip install "linuxfabrik-lib>=4.2.0"
```

Technical details

The vulnerability is an insecure temporary file creation (CWE-377) within the linuxfabrik-lib library used by various monitoring plugins. The software creates SQLite databases at predictable static paths in the /tmp directory without verifying if the path is already a symbolic link. A local attacker can create a symlink at these paths pointing to a target file; when the plugin runs (potentially with elevated privileges via sudo), it follows the symlink and writes its database content to the target. This can result in arbitrary file overwrites, denial of service, or corruption of existing SQLite databases via journal/WAL file manipulation. The issue is fixed in version 4.2.0 by implementing per-user temporary directories with strict ownership and permission checks.

Affected products

Linuxfabrik linuxfabrik-lib < 4.2.0

Identifiers

CVE-2026-53759
GHSA-r35r-fpx2-jgr4
PYSEC-2026-2596

Timeline

2026-06-02: disclosed: Initial disclosure to Linuxfabrik
2026-07-06: advisory: GitHub Advisory published
2026-07-06: patched: Fix released in version 4.2.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.