External risk intelligence

Burrito Operator Webhook Signature Bypass Leading to Unauthorized Terraform Plan Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-102649

The vulnerability affects an API endpoint designed to receive webhooks from external services like GitHub or GitLab. While these endpoints are intended to be network-reachable to function, they are typically configured to only accept traffic from specific, trusted webhook provider IP ranges rather than being open to the general public internet.

Missing Authentication

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability exists in Burrito, a Terraform Automation Collaboration Software (TACoS) Kubernetes operator, that could allow an attacker to forge events and trigger unauthorized infrastructure plan modifications. This could potentially expose or misattribute changes to infrastructure configurations by manipulating how the operator processes pull requests.

Forged events can alter infrastructure plans.
Affects automation software interacting with code repositories.
Confirm relevance and exposure of this automation software.

Attack Path

How an attacker could exploit the issue

An attacker can forge events to manipulate Terraform pull requests if they can reach the Burrito server and know a repository's URL. The vulnerability occurs when webhook secrets are not configured, allowing unsigned GitHub or GitLab events to be accepted. This can lead to unauthorized Terraform plans being generated and potentially commented on real pull requests, exposing infrastructure changes from different branches.

Accessible without authentication.
Triggered by forging webhook events.
Risk of exposing infrastructure changes.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to forge webhook events and create or delete Terraform resources. When supported, this could lead to unauthorized `terraform plan` executions for affected infrastructure layers, potentially exposing infrastructure changes from unintended branches. The attacker could also cause the plan to be posted to an unrelated pull request's comment thread.

Unauthorized `terraform plan` execution.
Forged webhook events targeting the API.
Exposure of infrastructure changes.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts the Burrito Terraform Automation Collaboration Software (TACoS) Kubernetes operator. The first practical step is for infrastructure or platform teams to identify all instances of Burrito, confirm their network reachability and criticality, and then locate the accountable owner for remediation. Coordination with vendor management may be necessary if Burrito was procured externally.

Platform and infrastructure teams own resolution.
Verify Burrito instance reachability and criticality.
Plan remediation with vendor and owner.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is Burrito and how is it used?

Burrito is a Kubernetes operator designed as Terraform Automation Collaboration Software (TACoS). It automates infrastructure workflows by connecting to code repositories like GitHub or GitLab. Teams use it to manage Terraform operations directly within a cluster, allowing the software to handle git-based events and perform automated infrastructure plans.

How does CVE-2026-102649 work?

This vulnerability involves a Missing Authentication for Critical Function (CWE-306) and Improper Authorization (CWE-863). The software fails to verify the cryptographic signatures of incoming webhook events if a secret is not configured. Without this check, the system blindly trusts forged event payloads sent to its API, allowing unauthorized modification of infrastructure states.

When can an attacker trigger this bug?

An attacker can trigger this by sending a crafted webhook request to the Burrito server if they know the URL of a tracked repository. The bug is only triggered when the 'webhookSecret' field is empty or unset. It does not trigger if a valid secret is configured, as the system then properly validates the authenticity of the incoming request before processing any data.

How do I know if I am at risk?

You should care if your Burrito instance is reachable from the network. According to Halo Surface Signal, while these API endpoints must be reachable to receive webhooks, they are often designed to accept traffic only from specific, trusted provider IP ranges. If your deployment is exposed to the broader internet or untrusted network segments, it is at higher risk of receiving malicious forged events.

What is the first step to remediate this?

The most important first step is to update your software to version 0.13.0 or later, which contains the fix. Before updating, your platform team should locate all running instances of Burrito to assess their current configuration, ensure that webhook secrets are enabled, and verify that network access controls are correctly restricting traffic to known, trusted sources.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.