GHSA-22W5-2FXG-VRWX
Vulnerability from github – Published: 2026-08-20 18:36 – Updated: 2026-08-20 18:36Impact
Unauthenticated denial of service.
Summary
When OpenTofu performs requests against an untrusted (or compromised) third-party server or connects to an attacker-controlled server, the initial connection negotiation can produce high CPU usage, leading to possible denial of service.
These vulnerabilities do not permit arbitrary code execution or allow disclosure of confidential information.
Details
OpenTofu relies on third-party implementations of TLS certificate verification and HTTP request execution from the standard library of the Go programming language.
The Go project has recently published the following advisories for those implementations which indirectly affect OpenTofu's behavior:
- CVE-2026-42504: Quadratic complexity in WordDecoder.DecodeHeader in mime
- CVE-2026-27145: Inefficient candidate hostname parsing in crypto/x509
CVE-2026-42504 affects OpenTofu's K8S remote state implementation. The operator of a configuration that uses such a backend needs to double-check the trustworthiness of the server used for this purpose. In situations where the server is untrusted or compromised, an attacker could configure it to respond with an intentionally crafted HTTP response designed to target this specific vulnerability in the Go standard library, potentially leading to high CPU usage.
CVE-2026-27145 has a similar outcome: if an untrusted or compromised third-party server is used, an attacker could craft a specific TLS certificate that targets this vulnerability in the Go standard library, which could also lead to high CPU usage.
Typical use of OpenTofu already requires caution in selection of third-party dependencies.
Patches
OpenTofu v1.11.9 and v1.12.2 address these vulnerabilities by upgrading to the Go versions that fix them (v1.25.11 and v1.26.3).
The OpenTofu v1.10 series is also impacted by these vulnerabilities. However, that series is built with a version of Go for which no upstream fix is available. Adopting Go 1.25.11 for that series would effectively end support for certain versions of macOS and Linux, and the OpenTofu Project has determined that the impact of these vulnerabilities is not high enough to justify that disruption in a patch release. For those using OpenTofu v1.10 releases, we recommend planning an upgrade to OpenTofu v1.11.9 in the near future.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/opentofu/opentofu"
},
"ranges": [
{
"events": [
{
"introduced": "1.12.0-beta1"
},
{
"fixed": "1.12.2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/opentofu/opentofu"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.11.9"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2026-08-20T18:36:22Z",
"nvd_published_at": null,
"severity": "LOW"
},
"details": "### Impact\n\nUnauthenticated denial of service.\n\n### Summary\n\nWhen OpenTofu performs requests against an untrusted (or compromised) third-party server or connects to an attacker-controlled server, the initial connection negotiation can produce high CPU usage, leading to possible denial of service.\n\nThese vulnerabilities **do not** permit arbitrary code execution or allow disclosure of confidential information.\n\n### Details\n\nOpenTofu relies on third-party implementations of TLS certificate verification and HTTP request execution from the standard library of the Go programming language.\n\nThe Go project has recently published the following advisories for those implementations which indirectly affect OpenTofu\u0027s behavior:\n\n- [CVE-2026-42504](https://www.cve.org/CVERecord?id=CVE-2026-42504): Quadratic complexity in WordDecoder.DecodeHeader in mime\n- [CVE-2026-27145](https://www.cve.org/CVERecord?id=CVE-2026-27145): Inefficient candidate hostname parsing in crypto/x509\n\nCVE-2026-42504 affects OpenTofu\u0027s K8S remote state implementation. The operator of a configuration that uses such a backend needs to double-check the trustworthiness of the server used for this purpose. \nIn situations where the server is untrusted or compromised, an attacker could configure it to respond with an intentionally crafted HTTP response designed to target this specific vulnerability in the Go standard library, potentially leading to high CPU usage.\n\nCVE-2026-27145 has a similar outcome: if an untrusted or compromised third-party server is used, an attacker could craft a specific TLS certificate that targets this vulnerability in the Go standard library, which could also lead to high CPU usage.\n\nTypical use of OpenTofu already requires caution in selection of third-party dependencies.\n\n### Patches\n\nOpenTofu v1.11.9 and v1.12.2 address these vulnerabilities by upgrading to the Go versions that fix them (v1.25.11 and v1.26.3).\n\nThe OpenTofu v1.10 series is also impacted by these vulnerabilities. However, that series is built with a version of Go for which no upstream fix is available. Adopting Go 1.25.11 for that series would effectively end support for certain versions of macOS and Linux, and the OpenTofu Project has determined that the impact of these vulnerabilities is not high enough to justify that disruption in a patch release. For those using OpenTofu v1.10 releases, we recommend planning an upgrade to OpenTofu v1.11.9 in the near future.",
"id": "GHSA-22w5-2fxg-vrwx",
"modified": "2026-08-20T18:36:22Z",
"published": "2026-08-20T18:36:22Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/opentofu/opentofu/security/advisories/GHSA-22w5-2fxg-vrwx"
},
{
"type": "WEB",
"url": "https://github.com/opentofu/opentofu/issues/4242"
},
{
"type": "WEB",
"url": "https://github.com/opentofu/opentofu/issues/4243"
},
{
"type": "WEB",
"url": "https://github.com/opentofu/opentofu/issues/4244"
},
{
"type": "PACKAGE",
"url": "https://github.com/opentofu/opentofu"
},
{
"type": "WEB",
"url": "https://github.com/opentofu/opentofu/releases/tag/v1.11.9"
},
{
"type": "WEB",
"url": "https://github.com/opentofu/opentofu/releases/tag/v1.12.2"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
}
],
"summary": "OpenTofu has high CPU usage when using K8S remote state backend or when parsing specifically crafted TLS certificates from untrusted or compromised servers"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.