How severe is CVE-2026-25499?

No CVSS score has been assigned to CVE-2026-25499 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-25499?

CVE-2026-25499 affects the following packages: github.com/bpg/terraform-provider-proxmox (Go). Ecosystems affected: Go.

How do I fix CVE-2026-25499?

Update github.com/bpg/terraform-provider-proxmox to 0.93.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25499 is resolved across your whole dependency graph.

How do I detect CVE-2026-25499 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bpg/terraform-provider-proxmox, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-25499 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-25499 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-25499 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-25499?

CVE-2026-25499 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-25499?

CVE-2026-25499 is classified as Path Traversal (CWE-22), CWE-1188 (CWE-1188). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-25499 published, and has it been updated?

CVE-2026-25499 was published on February 4, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2026-25499 — terraform-provider-proxmox

Fix: bpg/terraform-provider-proxmox@bd604c4

CVE-2026-25499 is a Path Traversal vulnerability in github.com/bpg/terraform-provider-proxmox. A fix is available for github.com/bpg/terraform-provider-proxmox — see the affected versions and patch details below.

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

Also known asGHSA-gwch-7m8v-7544GO-2026-4395

Published

Feb 4, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-25499.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/bpg/terraform-provider-proxmox

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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:

terraform ALL=(root) NOPASSWD: /usr/bin/tee /var/lib/vz/*

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:

terraform ALL=(root) NOPASSWD: /usr/bin/tee /var/lib/vz/snippets/[A-Za-z0-9-]*\\.yaml

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/bpg/terraform-provider-proxmox`	all versions	0.93.1`go get github.com/bpg/terraform-provider-proxmox@v0.93.1`

Affected Products

1 product · 1 configurations

Application

terraform providerbpg

< 0.93.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bpg/terraform-provider-proxmox, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/bpg/terraform-provider-proxmox to 0.93.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25499 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

> 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: ```bash terraform ALL=(root) NOPASSWD: /usr/bin/tee /var/lib/vz/* ``` 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/sudoer

O3 Security · Impact-Aware SCA

Is CVE-2026-25499 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works