Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/bpg/terraform-provider-proxmox

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.7GoPublished

    terraform-provider-proxmox has insecure sudo recommendation in the documentation

    CVE-2026-25499 · GHSA-gwch-7m8v-7544

    Affected
    • Go github.com/bpg/terraform-provider-proxmox < 0.93.1
    Fixed in
    0.93.1· Vendor fix available
    Issue
    Note: It is uncertain whether this constitutes a vulnerability or should be filed as an issue instead. Summary In the SSH configuration documentation, the sudoer line that was suggested can be escalated to edit any files in the system. Details The following line were suggested for addition in the sudoers file: But this is highly insecure as the folder can be escaped using ../ and any files can be edited on the system. PoC Using a terraform user with the previously mentioned line in the /etc/sudoers file, a /etc/sudoers.d/sudo file can be added using this command: echo "ALL=(ALL) NOPASSWD:ALL" | tee /var/lib/vz/../../../etc/sudoers.d/sudo This grants access to the full root of the node. Impact This breaches the access limits of the Terraform user. Suggested workaround Use a strict regex on the command to allow only the names that should be pushed by this user. Example for cloudinit yaml files:

    Recommended action: Upgrade to 0.93.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →