Intel

AIKIDO-2026-499176

filelock is vulnerable to Denial of Service (DoS)

Pre-CVE
Found by Aikido Intel before public disclosure or CVE publication.
Published Jul 20, 2026
July 20, 2026

55

CVE Score

Medium

Denial of Service (DoS)

Are you affected? Scan for Free

TL;DR

The SoftFileLease marker parser in _build_record reads a lease duration with float() and only rejects values that are non-positive, so a non-finite nan or inf duration passes as a valid lease record. A peer that can write to the shared lock filesystem plants a marker carrying duration=nan, which every contender then reads as a live claim. Because nan never equals any configured lease duration, each contender raises LeaseSettingsMismatch and the malformed marker is never reclaimed, wedging lock acquisition on that path. The fix rejects non-finite lease durations so such a marker is treated as malformed and ages out through the grace window instead.

How do I fix this?

Upgrade the filelock library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and use lease-based soft locks (SoftFileLease) on a filesystem that other parties can write to.

Package

Versions

3.30.0 - 3.30.0

Fixed in 3.30.1

Background info

filelock is vulnerable to Denial of Service (DoS) in versions 3.30.0 - 3.30.0.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea