CVEs.
Vulnerabilities published in the last two years in software made by the companies on the wall: clients, SDKs, agents and self-hosted editions. A CVE here does not mean the hosted service was affected or breached.
NVD data refreshed 1 h ago
Severity of matching CVEs
CVSS base severity, as scored in NVD
- Critical
- 7100%
- High
- 00%
- Medium
- 00%
- Low or not scored
- 00%
- Matching CVEs
- 7
- Last two years
- Critical
- 7
- CVSS 9.0 and above
- High
- 0
- CVSS 7.0 to 8.9
- Known exploited
- 0
- On CISA's KEV list
Matching CVEs published
By month, last two years
Peak 2 · July 2026
- Total: 7
- December 2024: 0
- January 2025: 1
- February 2025: 0
- March 2025: 0
- April 2025: 0
- May 2025: 0
- June 2025: 0
- July 2025: 0
- August 2025: 1
- September 2025: 0
- October 2025: 0
- November 2025: 1
- December 2025: 0
- January 2026: 0
- February 2026: 0
- March 2026: 0
- April 2026: 0
- May 2026: 0
- June 2026: 0
- July 2026: 2
- August 2026: 1
- September 2026: 0
- October 2026: 1
- November 2026: 0
Most CVEs
In each company's software, last two years
Matching CVEs
- 9.9Crit
CVE-2026-110720 (opens in a new tab)
Consul-k8s versions 0.42.0 and later are vulnerable to a cross-namespace authorization bypass in component ACL binding rules that may allow an attacker to obtain elevated Consul privileges. This vulnerability (CVE-2026-110720) is fixed in consul-k8s 2.1.0 and 1.8.18.
HashiCorp (HCP / Terraform Cloud)· Oct 26, 2026
- 9.6Crit
CVE-2026-8715 (opens in a new tab)
Vault Secrets Operator 1.3.0 up to 1.4.1 is vulnerable to an arbitrary file read and credential exfiltration issue in the AppRole authentication configuration that may allow a tenant with limited Kubernetes RBAC permissions to read files from the operator pod's filesystem and transmit their contents to a tenant-controlled endpoint, potentially leading to privilege escalation within the cluster. This vulnerability (CVE-2026-8715) is fixed in Vault Secrets Operator 1.5.0.
HashiCorp (HCP / Terraform Cloud)· Aug 13, 2026
- 10.0Crit
CVE-2026-16326 (opens in a new tab)
In consul-mcp-server, versions 0.1.0 up to 0.1.3 did not properly isolate session state in stateless mode, which may allow one client's Consul authentication token to be used for subsequent requests from other clients. This vulnerability (CVE-2026-16326) is fixed in consul-mcp-server 0.1.4.
HashiCorp (HCP / Terraform Cloud)· Jul 29, 2026
- 10.0Crit
CVE-2026-16498 (opens in a new tab)
The terraform-mcp-server before version 1.1.0 is vulnerable to a cross-tenant credential reuse issue in the streamable-HTTP stateless transport mode that may allow one user's Terraform token to be used to execute tool calls on behalf of subsequent users. This vulnerability, CVE-2026-16498, is fixed in terraform-mcp-server 1.1.0.
HashiCorp (HCP / Terraform Cloud)· Jul 28, 2026
- 9.8Crit
CVE-2025-13357 (opens in a new tab)
Vault’s Terraform Provider incorrectly set the default deny_null_bind parameter for the LDAP auth method to false by default, potentially resulting in an insecure configuration. If the underlying LDAP server allowed anonymous or unauthenticated binds, this could result in authentication bypass. This vulnerability, CVE-2025-13357, is fixed in Vault Terraform Provider v5.5.0.
HashiCorp (HCP / Terraform Cloud)· Nov 21, 2025
- 9.1Crit
CVE-2025-6000 (opens in a new tab)
A privileged Vault operator within the root namespace with write permission to {{sys/audit}} may obtain code execution on the underlying host if a plugin directory is set in Vault’s configuration. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.
HashiCorp (HCP / Terraform Cloud)· Aug 1, 2025
- 9.1Crit
CVE-2025-0377 (opens in a new tab)
HashiCorp’s go-slug library is vulnerable to a zip-slip style attack when a non-existing user-provided path is extracted from the tar entry.
HashiCorp (HCP / Terraform Cloud)· Jan 21, 2025
Public information only
Everything on this page was already published by the companies themselves or by public bodies. statuswall gathers it in one place, links every item to its original, and adds nothing from private or leaked sources.
Sources
- National Vulnerability Database (opens in a new tab): CVE IDs, descriptions, publication dates and CVSS severity, published by the U.S. government (NIST)
- CISA Known Exploited Vulnerabilities catalog (opens in a new tab): the "Known exploited" flag
How fresh it is
- New and changed CVEs: pulled from NVD every two hours; last run 1 h ago
- Known-exploited flags: updated from CISA in the same run
- Window: the last two years; older entries drop off automatically
Source: the U.S. National Vulnerability Database, refreshed daily, with the known-exploited flag from CISA's KEV catalog. Descriptions are NVD's. A CVE is listed under a company when NVD names that company's product as affected, or when the company's own CVE authority assigned it; companies whose names are common words are matched only by explicit rules, so some CVEs will be missing. This product uses NVD data but is not endorsed or certified by the NVD. CVE is a registered trademark of The MITRE Corporation.
statuswall is independent and is not affiliated with, sponsored by or endorsed by any company named here. Company and product names are used only to identify whose public information is being referred to. The information is provided as is, for general reference, with no guarantee that it is complete, current or free of error; it is not security, legal or purchasing advice. Where this page and an official source differ, the official source is right.