# CVE-2026-123025: An OS Command Injection vulnerability was discovered in the Google Cloud DNS validation module of the OPNsense os-acme-client plugin through 4.17.


- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-g9hg-38vq-jvh9

## What is CVE-2026-123025?

CVE-2026-123025 is a critical vulnerability in OPNsense os-acme-client, published on 5 Nov 2026. 

### Official description

An OS Command Injection vulnerability was discovered in the Google Cloud DNS validation module of the OPNsense os-acme-client plugin through 4.17. The DnsGcloud::prepare() method decodes the dns_gcloud_key model field and directly interpolates the string fields gcloud_account and gcloud_project into a shell command passed to proc_open() via LeUtils::run_shell_command() without any validation or escaping. A remote authenticated user with privileges to issue or renew certificates through the WebGUI/API can achieve arbitrary code execution as root.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-123025?


## How do I fix CVE-2026-123025?

No fix has been published for CVE-2026-123025 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-123025 being exploited?

There is no known exploitation of CVE-2026-123025 in the wild and no public exploit code.

Public exploit code:

- OS command injection as root via Google Cloud DNS challenge key (github_poc): https://github.com/cppghoul/CVE-2026-123025

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123025 and fix it if it is affected.

What it is: CVE-2026-123025 is a critical vulnerability in OPNsense os-acme-client, published on 5 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123025 in the wild and no public exploit code.

Affected product: OPNsense os-acme-client. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123025/ (Markdown: https://insights.sbomify.com/CVE-2026-123025/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123025
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123025
- OSV: https://osv.dev/vulnerability/CVE-2026-123025

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123025/
Summaries are generated and may contain mistakes; the official description above is the record.