# CVE-2026-65638: Improper escaping of a request URL in ConfigServer Security & Firewall allows an unauthenticated remote attacker to execute arbitrary comman


- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-8qv3-jfg8-cjvp

## What is CVE-2026-65638?

CVE-2026-65638 is a critical vulnerability in ConfigServer Security & Firewall, published on 10 Sep 2026. 

### Official description

Improper escaping of a request URL in  ConfigServer Security & Firewall allows an unauthenticated remote attacker to execute arbitrary commands as the CSF service account via shell command injection.

The vulnerability affects versions of the software originally distributed by ConfigServer, as well as versions of the WebPros-maintained fork that contain the vulnerable code. WebPros has addressed the vulnerability in version 16.30. Other forks or independently maintained versions of ConfigServer Security & Firewall (CSF) may also be affected and should be evaluated independently.

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

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


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

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

## Is CVE-2026-65638 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-65638 is a critical vulnerability in ConfigServer Security & Firewall, published on 10 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-65638 in the wild and no public exploit code.

Affected product: ConfigServer Security & Firewall. 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-65638/ (Markdown: https://insights.sbomify.com/CVE-2026-65638/index.md)
```

## Sources

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

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