CVE-2026-25499: CWE-1188: Insecure Default Initialization of Resource in bpg terraform-provider-proxmox
CVE-2026-25499 is a high-severity vulnerability in the terraform-provider-proxmox prior to version 0. 93. 1, involving insecure default initialization of resources. The issue arises from an insecure sudoer line suggested in the SSH configuration documentation, which allows directory traversal via '.. /' sequences. This flaw enables attackers to edit arbitrary files on the system without authentication or user interaction. The vulnerability has a CVSS 4. 0 score of 8. 7, indicating a network-exploitable, high-impact issue affecting integrity. It has been patched in version 0.
AI Analysis
Technical Summary
CVE-2026-25499 is a vulnerability identified in the terraform-provider-proxmox, a Terraform provider that facilitates infrastructure automation for the Proxmox Virtual Environment. The root cause is an insecure sudoer configuration line recommended in the SSH setup documentation prior to version 0.93.1. This insecure configuration allows an attacker to perform directory traversal attacks using '../' sequences, effectively escaping the intended directory context. As a result, an attacker can edit arbitrary files on the host system, compromising system integrity. The vulnerability is classified under CWE-1188 (Insecure Default Initialization of Resource) and CWE-22 (Path Traversal). The CVSS 4.0 vector indicates no privileges or user interaction are required, and the attack can be performed remotely over the network, making it highly exploitable. The vulnerability was reserved on February 2, 2026, and published on February 4, 2026. Although no known exploits are currently reported in the wild, the potential for widespread impact is significant due to the nature of Terraform and Proxmox usage in automating virtualized infrastructure. The issue has been addressed in version 0.93.1 of the provider, which corrects the insecure sudoer line and prevents directory traversal. Organizations using versions prior to 0.93.1 are advised to upgrade promptly to mitigate this risk.
Potential Impact
For European organizations, this vulnerability poses a serious risk to the integrity of virtualized infrastructure managed via Terraform and Proxmox. Exploitation could allow attackers to modify critical system files, potentially leading to unauthorized configuration changes, deployment of malicious code, or disruption of services. Given the widespread use of Proxmox in European data centers and enterprises for virtualization and container management, the impact could extend to cloud service providers, financial institutions, healthcare providers, and government agencies. The ability to exploit this vulnerability remotely without authentication increases the threat level, potentially enabling attackers to compromise multiple systems in automated environments. This could lead to data breaches, service outages, and loss of trust. The lack of known exploits in the wild suggests a window for proactive mitigation, but the high CVSS score and ease of exploitation necessitate urgent action.
Mitigation Recommendations
European organizations should immediately upgrade terraform-provider-proxmox to version 0.93.1 or later to apply the patch that fixes the insecure sudoer configuration. Review and audit all SSH sudoer configurations related to Proxmox automation to ensure they do not permit directory traversal or other insecure behaviors. Implement strict access controls on systems running Terraform and Proxmox, limiting who can modify infrastructure as code and execute automation scripts. Employ file integrity monitoring to detect unauthorized changes to critical system files. Use network segmentation to isolate management interfaces of Proxmox environments from general network access. Regularly review Terraform provider documentation and configurations for security best practices. Additionally, consider deploying runtime security tools that can detect anomalous file access patterns indicative of exploitation attempts. Finally, maintain an incident response plan tailored to infrastructure automation compromise scenarios.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Switzerland, Belgium, Italy
CVE-2026-25499: CWE-1188: Insecure Default Initialization of Resource in bpg terraform-provider-proxmox
Description
CVE-2026-25499 is a high-severity vulnerability in the terraform-provider-proxmox prior to version 0. 93. 1, involving insecure default initialization of resources. The issue arises from an insecure sudoer line suggested in the SSH configuration documentation, which allows directory traversal via '.. /' sequences. This flaw enables attackers to edit arbitrary files on the system without authentication or user interaction. The vulnerability has a CVSS 4. 0 score of 8. 7, indicating a network-exploitable, high-impact issue affecting integrity. It has been patched in version 0.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-25499 is a vulnerability identified in the terraform-provider-proxmox, a Terraform provider that facilitates infrastructure automation for the Proxmox Virtual Environment. The root cause is an insecure sudoer configuration line recommended in the SSH setup documentation prior to version 0.93.1. This insecure configuration allows an attacker to perform directory traversal attacks using '../' sequences, effectively escaping the intended directory context. As a result, an attacker can edit arbitrary files on the host system, compromising system integrity. The vulnerability is classified under CWE-1188 (Insecure Default Initialization of Resource) and CWE-22 (Path Traversal). The CVSS 4.0 vector indicates no privileges or user interaction are required, and the attack can be performed remotely over the network, making it highly exploitable. The vulnerability was reserved on February 2, 2026, and published on February 4, 2026. Although no known exploits are currently reported in the wild, the potential for widespread impact is significant due to the nature of Terraform and Proxmox usage in automating virtualized infrastructure. The issue has been addressed in version 0.93.1 of the provider, which corrects the insecure sudoer line and prevents directory traversal. Organizations using versions prior to 0.93.1 are advised to upgrade promptly to mitigate this risk.
Potential Impact
For European organizations, this vulnerability poses a serious risk to the integrity of virtualized infrastructure managed via Terraform and Proxmox. Exploitation could allow attackers to modify critical system files, potentially leading to unauthorized configuration changes, deployment of malicious code, or disruption of services. Given the widespread use of Proxmox in European data centers and enterprises for virtualization and container management, the impact could extend to cloud service providers, financial institutions, healthcare providers, and government agencies. The ability to exploit this vulnerability remotely without authentication increases the threat level, potentially enabling attackers to compromise multiple systems in automated environments. This could lead to data breaches, service outages, and loss of trust. The lack of known exploits in the wild suggests a window for proactive mitigation, but the high CVSS score and ease of exploitation necessitate urgent action.
Mitigation Recommendations
European organizations should immediately upgrade terraform-provider-proxmox to version 0.93.1 or later to apply the patch that fixes the insecure sudoer configuration. Review and audit all SSH sudoer configurations related to Proxmox automation to ensure they do not permit directory traversal or other insecure behaviors. Implement strict access controls on systems running Terraform and Proxmox, limiting who can modify infrastructure as code and execute automation scripts. Employ file integrity monitoring to detect unauthorized changes to critical system files. Use network segmentation to isolate management interfaces of Proxmox environments from general network access. Regularly review Terraform provider documentation and configurations for security best practices. Additionally, consider deploying runtime security tools that can detect anomalous file access patterns indicative of exploitation attempts. Finally, maintain an incident response plan tailored to infrastructure automation compromise scenarios.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-02T18:21:42.485Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6983afd6f9fa50a62fabdb3a
Added to database: 2/4/2026, 8:45:10 PM
Last enriched: 2/12/2026, 7:27:27 AM
Last updated: 3/22/2026, 3:55:44 AM
Views: 266
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.