Skip to content
VulniPulse
Medium5.3Red Hat Linux

CVE-2026-112908: Red Hat unauthorized concurrent access via insecure claim directory permissions

This Red Hat advisory covers CVE-2026-112908. Related products: Red Hat Ansible Automation Platform 2.

Open the Red Hat advisory

Key facts

Vendor rating
Medium, CVSS 5.3
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L · base score 5.3, scored by GitHub_MAttack vector: local. Attack complexity: high. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: high. Availability impact: low.
Weakness
  • CWE-732: Incorrect Permission Assignment for Critical Resource
EPSS
0.12% chance of exploitation in the next 30 days (1st percentile). FIRST EPSS, .
CISA SSVC
Exploitation: proof of concept exists. Automatable: no. Technical impact: partial. CISA, .
CISA KEV
Not listed (catalogue checked )
Fixed in
4.2.1
Source published
Listed by VulniPulse

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Related products & platforms

Red Hat LinuxUnclassified

Description

unauthorized concurrent access via insecure claim directory permissions. Red Hat rates this moderate (CVSS 5.3).

Weakness: CWE-279.

Affected product named by the advisory: Red Hat Ansible Automation Platform 2.

Text from the source record.

How to fix CVE-2026-112908

Upgrade to a fixed release named by Red Hat:

  • 4.2.1

Vendor guidance

  • Configure processes that employ filelock to run with a restrictive umask (such as 022 or 027) and store lock files in dedicated, user-owned directories rather than shared world-writable directories such as /tmp. Additionally, verify that parent directories do not enforce default POSIX ACLs that grant write permissions to other users or groups. To apply a restrictive umask to an application process or session: ```bash umask 027 ``` To remove group and world write permissions on existing lock coordination trees: ```bash find /path/to/locks -maxdepth 2 -type d -name '*.filelock' -exec chmod -R go-w {} + ``` Enforcing restrictive umasks or removing write permissions will prevent legitimate cross-account lock sharing if an application intentionally relies on group-writable coordination files. Permission modifications should be executed while associated workloads are idle to avoid disrupting active synchronization.

All Red Hat Linux advisories

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Red Hat