{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-102649 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102649 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102649 is a critical vulnerability in padok-team burrito, published on 26 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-102649 and fix it if it is affected.\n\nWhat it is: CVE-2026-102649 is a critical vulnerability in padok-team burrito, published on 26 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-102649 in the wild and no public exploit code.\n\nAffected product: padok-team burrito. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-102649/ (Markdown: https://insights.sbomify.com/CVE-2026-102649/index.md)","id":"CVE-2026-102649","markdown":"https://insights.sbomify.com/CVE-2026-102649/index.md","name":"CVE-2026-102649","record":{"aliases":["GHSA-7m68-72r6-3jx8"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Burrito is a Terraform Automation Collaboration Software (TACoS) Kubernetes operator. Prior to 0.13.0, `POST /api/webhook` accepts unsigned GitHub and GitLab events when a `TerraformRepository`'s credentials omit `webhookSecret` or set it to an empty value, including credentials configured for git authentication and polling. `Credential.WebhookSecret` is optional, and `go-playground/webhooks` skips signature or token verification when the secret is empty. Anyone who can reach `burrito-server`'s endpoint and knows a tracked repository's URL can forge events to create or delete `TerraformPullRequest` custom resources with attacker-chosen `Branch`, `Base`, and `ID` fields. For GitHub `pull_request` events, the controller fetches changed files using the real pull request number but does not cross-check the payload's branch against that pull request. Pairing a real, existing pull request number with an unrelated existing branch in the same repository can therefore cause an unauthorized `terraform plan` for affected layers using the operator's stored git and cloud credentials. Code analysis also indicates that the resulting plan can be posted to the real pull request's comment thread, exposing and misattributing another branch's infrastructure changes. Auto-apply is disabled for these temporary layers, so this vulnerability alone cannot force a `terraform apply`; plan-time provider and data-source code execution depends on the selected branch's contents. This issue is fixed in version 0.13.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Burrito: Unauthenticated webhooks trigger unauthorized Terraform plans when webhookSecret is unset","id":"CVE-2026-102649","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"OpenList: Search metadata/count disclosure via Non-Separator-Aware Path Check in Bleve Search","id":"CVE-2026-102663"},"packages":[],"prev":{"headline":"MobilityDB through 1.3.0 Out-of-bounds Read DoS via WKB Deserialization","id":"CVE-2026-102639"},"products":["burrito"],"published":"2026-10-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-26","vendors":["padok-team"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-102649/"}