EUVD-2026-80121Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
Authenticated project member required (PR:L) and precise parameter crafting needed (AC:H); low file-disclosure and possible availability impact.
Primary rating from Vendor (GitLab).
CVSS VectorVendor: GitLab
Lifecycle Timeline
4DescriptionCVE.org
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could have allowed an authenticated user with project-level permissions to access restricted file contents on the server or cause denial of service due to improper validation of parameters in the Terraform state upload functionality.
AnalysisAI
Improper validation of parameters in GitLab CE/EE's Terraform state upload functionality allows an authenticated user holding project-level permissions to read restricted file contents on the server or cause denial of service. Affected releases are all versions from 18.2.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2, with fixes published in the 19.3.2 patch release. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires an authenticated GitLab account holding project-level permissions sufficient to write to the Terraform state backend (GitLab's Developer role and above can push state to a project's state endpoint; CVSS PR:L confirms authenticated, non-admin access). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals conflict and should be read carefully. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade to a fixed release: GitLab 19.1.8, 19.2.6, or 19.3.2 (the earliest fix on each affected branch). … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
aws/resource_aws_iam_user_login_profile.go in the HashiCorp Terraform Amazon Web Services (AWS) provider through v1.12.0
HashiCorp Terraform Enterprise releases up to v202106-1 did not properly perform authorization checks on a subset of API
Terraform version 1.0.8 through 1.5.6 allows arbitrary file write during the `init` operation if run on maliciously craf
When using the Azure backend with a shared access signature (SAS), Terraform versions prior to 0.12.17 may transmit the
The Terraform Provider for Linode prior to version 3.9.0 exposes sensitive credentials including passwords and API token
Terraform state versions can be created by a user with specific but insufficient permissions in a Terraform Enterprise w
Same technique Denial Of Service
View allShare
External POC / Exploit Code
Leaving vuln.today