Skip to content
VulniPulse
Advisory severityMedium6.1Red Hat Linux

Medium [CVE-2026-74796] Arbitrary file write via symlink following path traversal

This medium-severity Red Hat Linux advisory covers CVE-2026-74796.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-74796 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

OpenTofu before 1.11.7 fails to validate existing symlinks in the provider cache directory during initialization. Attackers can place a malicious symlink in a trusted working directory to cause tofu init to write provider package contents to arbitrary filesystem locations outside the working tree.

A flaw was found in OpenTofu. This vulnerability allows attackers to exploit a symlink following path traversal during the initialization process.

This could lead to unauthorized modification of files on the system. This Moderate flaw in OpenTofu allows for arbitrary file writes via symlink following during initialization.

However, Red Hat products are not affected by this vulnerability as the vulnerable code is not present. Red Hat severity: Moderate — CVSS 6.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:H/A:N).

Weakness: CWE-59. Red Hat lists Red Hat Hardened Images as not affected.

Affected versions
  • < 1.11.7

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · high-confidence parse· fetched 24 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.