<?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://db.gcve.eu</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>Sun, 25 Oct 2026 22:45:45 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-112906</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-112906</link>
      <description>&lt;p&gt;filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching modification times preserve the observation, and an honest contender creates a fresh marker on the reused inode, causing that live marker to be removed as stale. 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 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching modification times preserve the observation, and an honest contender creates a fresh marker on the reused inode, causing that live marker to be removed as stale. This issue is fixed in version 4.2.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-112906</guid>
    </item>
    <item>
      <title>GHSA-2g95-wg33-c5x2 — filelock: SoftFileLock evicts a fresh lock file whose watched age another local user's pre-dated file passed on through…</title>
      <link>https://db.gcve.eu/vuln/ghsa-2g95-wg33-c5x2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: filelock&lt;/p&gt;
&lt;p&gt;`SoftFileLock` and `MarkerSoftFileLock` evict an unparsable marker (the lock file at `&amp;lt;path&amp;gt;`, whose presence says a process holds the lock) once a waiting contender has watched it unchanged for two seconds. `SoftFileLease` expires a lease the same way. The watch tells two looks apart by the marker&amp;#39;s modification time (mtime) and inode number (the kernel&amp;#39;s identity for a file, independent of its name) alone.&lt;/p&gt;
&lt;p&gt;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), parks an empty file of its own at the lock path. It dates that file to a future tick of the kernel&amp;#39;s coarse clock (a clock that advances in steps of 4 ms), lets the waiters of the user running the lock (the lock user below) watch it past two seconds, and unlinks it in that tick. On a filesystem that hands a freed inode number straight back (ext4, overlayfs on ext4) the lock user&amp;#39;s next marker repeats both values. It inherits the time spent watching the other user&amp;#39;s file, and a second waiter removes it while its owner holds the lock.&lt;/p&gt;
&lt;p&gt;Two of the lock user&amp;#39;s processes then run the critical section together with no error. A `SoftFileLease` waiter takes a live lease that its owner wrote moments before, within milliseconds instead of after `lease_duration`. Affected versions: filelock &amp;gt;= 4.1.0 and &amp;lt;= 4.2.0 (finding `ANT-2026-RKC48J5B`).&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:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: filelock&lt;/p&gt;
&lt;p&gt;`SoftFileLock` and `MarkerSoftFileLock` evict an unparsable marker (the lock file at `&amp;lt;path&amp;gt;`, whose presence says a process holds the lock) once a waiting contender has watched it unchanged for two seconds. `SoftFileLease` expires a lease the same way. The watch tells two looks apart by the marker&amp;#39;s modification time (mtime) and inode number (the kernel&amp;#39;s identity for a file, independent of its name) alone.&lt;/p&gt;
&lt;p&gt;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), parks an empty file of its own at the lock path. It dates that file to a future tick of the kernel&amp;#39;s coarse clock (a clock that advances in steps of 4 ms), lets the waiters of the user running the lock (the lock user below) watch it past two seconds, and unlinks it in that tick. On a filesystem that hands a freed inode number straight back (ext4, overlayfs on ext4) the lock user&amp;#39;s next marker repeats both values. It inherits the time spent watching the other user&amp;#39;s file, and a second waiter removes it while its owner holds the lock.&lt;/p&gt;
&lt;p&gt;Two of the lock user&amp;#39;s processes then run the critical section together with no error. A `SoftFileLease` waiter takes a live lease that its owner wrote moments before, within milliseconds instead of after `lease_duration`. Affected versions: filelock &amp;gt;= 4.1.0 and &amp;lt;= 4.2.0 (finding `ANT-2026-RKC48J5B`).&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:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-2g95-wg33-c5x2</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-112906</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-112906</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 4.1.0 un ...)&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 4.1.0 un ...)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-112906</guid>
    </item>
  </channel>
</rss>
