<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 17 Nov 2026 02:27:53 +0000</lastBuildDate>
    <item>
      <title>BREW-ansible-lint-CVE-2026-112935 — filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders</title>
      <link>https://cve.radiocsirt.org/vuln/brew-ansible-lint-cve-2026-112935</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: ansible-lint&lt;/p&gt;
&lt;p&gt;The stale-lock break shared by `SoftFileLock`, `MarkerSoftFileLock` and `SoftFileLease` (and their async variants, and a `FileLock` that has fallen back to a soft lock on `ENOSYS`, the &amp;#34;not implemented&amp;#34; error) recognises the marker it judged stale by two values. The marker is the lock file at `&amp;lt;path&amp;gt;`, whose presence says a process holds the lock. The values are its inode number (the kernel&amp;#39;s identity for a file, independent of its name) and its modification time (mtime) not being newer. The check runs after the contender has already closed the marker, so nothing keeps the inode allocated.&lt;/p&gt;
&lt;p&gt;On a filesystem that hands a freed inode number straight to the next file (ext4, xfs, overlayfs on them) the next holder&amp;#39;s marker can carry that number. A contender still between its read and its break then renames and unlinks the live marker. Another local user (the other user below) who can create files in the lock&amp;#39;s directory, a sticky `/tmp` included (the sticky bit is a directory flag that lets only a file&amp;#39;s owner remove it), forces this at will. It plants a marker with a stale owner record and a modification time in the future and unlinks it as soon as a contender has read it. Two processes of the user running the lock (the lock user below) then hold the same default-configured lock at once, and nothing raises or logs. Affected versions: filelock &amp;gt;= 3.22.0 and &amp;lt;= 4.2.0 (finding `ANT-2026-KIIS96IX`).&lt;/p&gt;
&lt;p&gt;## Severity&lt;/p&gt;
&lt;p&gt;**CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N, 4.7 (Medium).**&lt;/p&gt;
&lt;p&gt;`AV:L…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: ansible-lint&lt;/p&gt;
&lt;p&gt;The stale-lock break shared by `SoftFileLock`, `MarkerSoftFileLock` and `SoftFileLease` (and their async variants, and a `FileLock` that has fallen back to a soft lock on `ENOSYS`, the &amp;#34;not implemented&amp;#34; error) recognises the marker it judged stale by two values. The marker is the lock file at `&amp;lt;path&amp;gt;`, whose presence says a process holds the lock. The values are its inode number (the kernel&amp;#39;s identity for a file, independent of its name) and its modification time (mtime) not being newer. The check runs after the contender has already closed the marker, so nothing keeps the inode allocated.&lt;/p&gt;
&lt;p&gt;On a filesystem that hands a freed inode number straight to the next file (ext4, xfs, overlayfs on them) the next holder&amp;#39;s marker can carry that number. A contender still between its read and its break then renames and unlinks the live marker. Another local user (the other user below) who can create files in the lock&amp;#39;s directory, a sticky `/tmp` included (the sticky bit is a directory flag that lets only a file&amp;#39;s owner remove it), forces this at will. It plants a marker with a stale owner record and a modification time in the future and unlinks it as soon as a contender has read it. Two processes of the user running the lock (the lock user below) then hold the same default-configured lock at once, and nothing raises or logs. Affected versions: filelock &amp;gt;= 3.22.0 and &amp;lt;= 4.2.0 (finding `ANT-2026-KIIS96IX`).&lt;/p&gt;
&lt;p&gt;## Severity&lt;/p&gt;
&lt;p&gt;**CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N, 4.7 (Medium).**&lt;/p&gt;
&lt;p&gt;`AV:L…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-ansible-lint-cve-2026-112935</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-CH96259 — filelock is a platform-independent file lock for Python</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-ch96259</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: litellm-database&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the litellm-database package. filelock is a platform-independent file lock for Python.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: litellm-database&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the litellm-database package. filelock is a platform-independent file lock for Python.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-ch96259</guid>
    </item>
    <item>
      <title>EUVD-2026-394186</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-394186</link>
      <description>EUVD-2026-394186</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-394186</guid>
    </item>
    <item>
      <title>fkie_cve-2026-112935</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-112935</link>
      <description>&lt;p&gt;filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor&amp;#39;s modification time is not newer than the saved observation, causing the live marker to be removed and two holders to be admitted. This issue is fixed in version 4.2.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor&amp;#39;s modification time is not newer than the saved observation, causing the live marker to be removed and two holders to be admitted. This issue is fixed in version 4.2.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-112935</guid>
    </item>
    <item>
      <title>GHSA-fq56-3cx3-fjxp — filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fq56-3cx3-fjxp</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: filelock&lt;/p&gt;
&lt;p&gt;The stale-lock break shared by `SoftFileLock`, `MarkerSoftFileLock` and `SoftFileLease` (and their async variants, and a `FileLock` that has fallen back to a soft lock on `ENOSYS`, the &amp;#34;not implemented&amp;#34; error) recognises the marker it judged stale by two values. The marker is the lock file at `&amp;lt;path&amp;gt;`, whose presence says a process holds the lock. The values are its inode number (the kernel&amp;#39;s identity for a file, independent of its name) and its modification time (mtime) not being newer. The check runs after the contender has already closed the marker, so nothing keeps the inode allocated.&lt;/p&gt;
&lt;p&gt;On a filesystem that hands a freed inode number straight to the next file (ext4, xfs, overlayfs on them) the next holder&amp;#39;s marker can carry that number. A contender still between its read and its break then renames and unlinks the live marker. Another local user (the other user below) who can create files in the lock&amp;#39;s directory, a sticky `/tmp` included (the sticky bit is a directory flag that lets only a file&amp;#39;s owner remove it), forces this at will. It plants a marker with a stale owner record and a modification time in the future and unlinks it as soon as a contender has read it. Two processes of the user running the lock (the lock user below) then hold the same default-configured lock at once, and nothing raises or logs. Affected versions: filelock &amp;gt;= 3.22.0 and &amp;lt;= 4.2.0 (finding `ANT-2026-KIIS96IX`).&lt;/p&gt;
&lt;p&gt;## Severity&lt;/p&gt;
&lt;p&gt;**CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N, 4.7 (Medium).**&lt;/p&gt;
&lt;p&gt;`AV:L…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: filelock&lt;/p&gt;
&lt;p&gt;The stale-lock break shared by `SoftFileLock`, `MarkerSoftFileLock` and `SoftFileLease` (and their async variants, and a `FileLock` that has fallen back to a soft lock on `ENOSYS`, the &amp;#34;not implemented&amp;#34; error) recognises the marker it judged stale by two values. The marker is the lock file at `&amp;lt;path&amp;gt;`, whose presence says a process holds the lock. The values are its inode number (the kernel&amp;#39;s identity for a file, independent of its name) and its modification time (mtime) not being newer. The check runs after the contender has already closed the marker, so nothing keeps the inode allocated.&lt;/p&gt;
&lt;p&gt;On a filesystem that hands a freed inode number straight to the next file (ext4, xfs, overlayfs on them) the next holder&amp;#39;s marker can carry that number. A contender still between its read and its break then renames and unlinks the live marker. Another local user (the other user below) who can create files in the lock&amp;#39;s directory, a sticky `/tmp` included (the sticky bit is a directory flag that lets only a file&amp;#39;s owner remove it), forces this at will. It plants a marker with a stale owner record and a modification time in the future and unlinks it as soon as a contender has read it. Two processes of the user running the lock (the lock user below) then hold the same default-configured lock at once, and nothing raises or logs. Affected versions: filelock &amp;gt;= 3.22.0 and &amp;lt;= 4.2.0 (finding `ANT-2026-KIIS96IX`).&lt;/p&gt;
&lt;p&gt;## Severity&lt;/p&gt;
&lt;p&gt;**CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N, 4.7 (Medium).**&lt;/p&gt;
&lt;p&gt;`AV:L…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fq56-3cx3-fjxp</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-112935</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-112935</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: python-filelock, Ubuntu:Pro:20.04:LTS: python-filelock, Ubuntu:Pro:22.04:LTS: python-filelock, Ubuntu:Pro:24.04:LTS: python-filelock, Ubuntu:26.10: python-filelock, Ubuntu:26.04:LTS: python-filelock&lt;/p&gt;
&lt;p&gt;filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor&amp;#39;s modification time is not newer than the saved observation, causing the live marker to be removed and two holders to be admitted. This issue is fixed in version 4.2.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: python-filelock, Ubuntu:Pro:20.04:LTS: python-filelock, Ubuntu:Pro:22.04:LTS: python-filelock, Ubuntu:Pro:24.04:LTS: python-filelock, Ubuntu:26.10: python-filelock, Ubuntu:26.04:LTS: python-filelock&lt;/p&gt;
&lt;p&gt;filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor&amp;#39;s modification time is not newer than the saved observation, causing the live marker to be removed and two holders to be admitted. This issue is fixed in version 4.2.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-112935</guid>
    </item>
  </channel>
</rss>
