Affected Systems
HashiCorp Terraform MCP Server versions 0.2.1–1.0.0 (Streamable HTTP mode only); Veeam Service Provider Console versions 9.2.1.33875 and earlier (all version 9 builds before 9.3); Django versions prior to 6.0.8 and 5.2.17 (GeoDjango spatial field configurations with staff user access).
Exploitation Status
No active exploitation reported as of August 5, 2026. Not listed in CISA KEV catalog. No public proof-of-concept code available. Veeam CVE-2026-58073 rated high attack complexity despite unauthenticated vector.
Business Impact
Terraform MCP Server CVE-2026-16498 (CVSS 10.0) enables cross-tenant credential reuse in stateless HTTP mode, allowing one user's token to access another tenant's infrastructure. Veeam VSPC CVE-2026-58073 (CVSS 9.5) permits unauthenticated attackers to impersonate managed agents and steal credentials, threatening MSP and hosting provider environments. Django flaw allows file write and potential code execution via GeoDjango spatial lookups by authenticated staff users. All three vendors have released patches. Exposure is configuration-dependent: Terraform bugs affect only Streamable HTTP deployments (not stdio mode), Veeam flaws affect version 9 pre-9.3 builds, and Django requires staff account with view permission on spatial field models.
Urgency
🟠 Within 24 hours
Recommended Actions
- Update HashiCorp Terraform MCP Server to version 1.1.0 or later immediately if running Streamable HTTP mode; stdio-only deployments are unaffected
- Upgrade Veeam Service Provider Console to build 9.3.0.35057 for all version 9 installations; prioritize internet-facing VSPC instances
- Patch Django to version 6.0.8 or 5.2.17 if using GeoDjango with spatial fields accessible to staff users
- Review Terraform MCP Server logs for unexpected cross-tenant access patterns or session anomalies in stateless and stateful HTTP modes
- Audit Veeam VSPC managed agent authentication logs for impersonation attempts or credential exposure events since May 2026