CVE-2026-112939

Description

A flaw was found in filelock. The SoftFileLock component can trust a forged process identifier (PID) in a lock marker file that an attacker can modify. A local attacker can exploit this flaw to cause an authorized process to act as a confused deputy, improperly removing an active lock marker and admitting another contender. This issue can result in unauthorized lock release and concurrent file access, compromising data integrity.

Statement

This vulnerability is rated as Moderate impact for Red Hat products because exploitation requires local system access alongside specific, non-default file permission settings. Standard Red Hat enterprise environments enforce restrictive default umasks that prevent unauthorized local accounts from modifying lock markers owned by other processes. Risk is confined to scenarios where applications explicitly configure shared write permissions within sticky directories, potentially allowing an unprivileged local user to trigger premature lock release and concurrent access to locked resources.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.7N/A4.7
Attack VectorLocalN/ALocal
Attack ComplexityHighN/AHigh
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactHighN/AHigh
Availability ImpactNoneN/ANone

Vector

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

cve.org: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N

Understanding the Weakness (CWE)

Confidentiality,Access Control,Availability

Technical Impact: Bypass Protection Mechanism; Gain Privileges or Assume Identity; Varies by Context

When security decisions such as authentication and authorization are made based on the values of these inputs, attackers can bypass the security of the product to access whatever is being protected. An attacker could change these inputs using customized clients or other attacks. This change might not be detected. The consequences will depend on the associated functionality, but they can range from granting additional privileges to untrusted users to bypassing important security checks. Ultimately, this weakness may lead to exposure or modification of sensitive data, system crash, or execution of arbitrary code.

Frequently Asked Questions

Want to get errata notifications? Sign up here.