Security Bulletin
Summary
Terraform state versions can be created by a user with specific but insufficient permissions in a Terraform Enterprise workspace. This may allow for the alteration of infrastructure if a subsequent plan operation is approved by a user with approval permission or is auto-applied. This vulnerability, CVE-2025-13432, is fixed in Terraform Enterprise version 1.1.1 and 1.0.3.
Vulnerability Details
CVEID: CVE-2025-13432
Description: Terraform state versions can be created by a user with specific but insufficient permissions in a Terraform Enterprise workspace. This may allow for the alteration of infrastructure if a subsequent plan operation is approved by a user with approval permission or auto-applied. This vulnerability, CVE-2025-13432, is fixed in Terraform Enterprise version 1.1.1 and 1.0.3.
CWE: CWE-863 Incorrect Authorization
CVSS Source: HashiCorp Inc.
CVSS Base score: 4.3
CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N)
Affected Products and Versions
| Affected Product(s) | Version(s) |
| Terraform Enterprise | 1.1.0, 1.0.2 |
Remediation/Fixes
Customers should evaluate the risk associated with this issue and consider upgrading to Terraform Enterprise version 1.1.1 or 1.0.3.
Get Notified about Future Security Bulletins
References
Link to HashiCorp bulletin
A user, who is part of a Team that holds "Lock/Unlock workspace" permission and a combination of "View all workspaces" organization level permission or "Read" state access at the project or workspace level, can write a new state version within a workspace. Organization permission to "Manage all workspaces" or "Manage all projects" implicitly grants permission to lock or unlock a workspace. This combination of permissions allows a user to create a new state version after locking a workspace, even if the user does not have "write" state access permission. Creating a new state version that differs from the previous version may cause a subsequent Terraform apply operation to alter infrastructure if the plan operation is approved by a user or is auto-applied. All infrastructure operations are correctly represented in the plan output. Previous state versions are not deleted or modified and can be rolled back to at any point.
We deeply appreciate any effort to coordinate disclosure of security vulnerabilities. For information about security at HashiCorp and the reporting of security vulnerabilities, please see https://hashicorp.com/security.
Acknowledgement
This issue was identified by a third party who reported it to HashiCorp.
Change History
21 Nov 2025: Initial Publication
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.
Disclaimer
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES ""AS IS"" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. In addition to other efforts to address potential vulnerabilities, IBM periodically updates the record of components contained in our product offerings. As part of that effort, if IBM identifies previously unidentified packages in a product/service inventory, we address relevant vulnerabilities regardless of CVE date. Inclusion of an older CVEID does not demonstrate that the referenced product has been used by IBM since that date, nor that IBM was aware of a vulnerability as of that date. We are making clients aware of relevant vulnerabilities as we become aware of them. "Affected Products and Versions" referenced in IBM Security Bulletins are intended to be only products and versions that are supported by IBM and have not passed their end-of-support or warranty date. Thus, failure to reference unsupported or extended-support products and versions in this Security Bulletin does not constitute a determination by IBM that they are unaffected by the vulnerability. Reference to one or more unsupported versions in this Security Bulletin shall not create an obligation for IBM to provide fixes for any unsupported or extended-support products or versions.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
21 November 2025
Initial Publish date:
21 November 2025
UID
ibm17252296