CVE-2026-112941VulnerabilityPublished 29 Oct 2026

hatch · filelock: SoftReadWriteLock follows a lock tree swapped in after its first acquire and writes lock records into

Affects hatchSource GCVE Database

Compare

Authoritative record:CVE-2026-112941· Low 3.3

Not known to be exploited · CVSS 3.3 Low : upgrade to 1.18.1_2 when convenient.

Data as of 30 Oct 2026, 09:00 UTC

CVSS 3.1 base score

3.3Low

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	3.3

Patch: Available – fixed in 1.18.1_2

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade hatch to 1.18.1_2.

Affected software

Product	Affected	Fixed in
Homebrewhatch`pkg:brew/hatch`Other threats	Affected >=1.18.1_1 <1.18.1_2	Fixed in 1.18.1_2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in hatch version 1.18.1_2 that fixes this vulnerability. Users should upgrade to this version or later to remediate the issue. No additional mitigation steps are required beyond applying the official fix.

Description

CVE-2026-112941 is a local integrity vulnerability in the SoftReadWriteLock implementation used by the hatch product. It allows a local user with write access to the lock's parent directory to replace the lock's directory tree with symbolic links after the first lock acquisition, causing the lock user process to write lock records into attacker-controlled locations. This results in the lock user's files being replaced or deleted, breaking functionality such as a git repository's operation. The vulnerability affects hatch versions >=1.18.1_1 and <1.18.1_2 on POSIX and Windows platforms. The CVSS score is 3.3 (low severity) due to local attack vector, low integrity impact, and no confidentiality or availability impact. A fix is available in version 1.18.1_2.

Impact

An unprivileged local user with write access to the lock's parent directory can cause a long-running process using SoftReadWriteLock to write lock records into attacker-controlled symbolic link targets, resulting in deletion or replacement of files owned by the lock user. This compromises data integrity by breaking the expected file structure (e.g., corrupting a git repository), but does not disclose confidential information or affect availability. The attack requires local access and specific directory write permissions, limiting its scope.

Summary

The SoftReadWriteLock and AsyncSoftReadWriteLock classes check once per lock object that certain directories (<path>.rw, <path>.rw/gen, <path>.rw/holders) are real directories and not symbolic links, storing only a boolean result. Subsequent operations resolve the full path again but only protect the last component from symbolic links via O_NOFOLLOW. A local attacker with write access to the lock's parent directory or who created the <path>.rw directory in a sticky directory (e.g., /tmp) can replace the gen or holders directories with symbolic links pointing into the lock user's writable directory. A long-running lock user process that has passed the initial check then performs file operations (create, rename, delete) on these paths with its own privileges, causing files to be replaced or deleted unexpectedly. This breaks integrity of the lock user's files (e.g., a git repository's HEAD file), but does not expose confidential data or affect availability. The vulnerability requires local access and write permissions on the lock's parent directory and affects hatch versions >=1.18.1_1 and <1.18.1_2. The issue is fixed in version 1.18.1_2.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 09:00 UTC

Technical details

References

Community reviews

Related threats