● High · CVSS 8.2

How to Fix CVE-2026-0805: Path Traversal in Crafty Controller

Q: Is CVE-2026-0805 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Q: Will a WAF or IDS rule fully mitigate CVE-2026-0805?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Q: How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for Crafty Controller run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-0830: Command Injection in Kiro IDE — Command Injection in Kiro IDE
How to Fix CVE-2026-35902: n/a in n/a — n/a in n/a
How to Fix CVE-2026-7601: Denial of Service in Open5GS , Denial of Service in Open5GS
How to Fix CVE-2026-42396: Code Injection RCE in Authoritative , Code Injection RCE in Authoritative
How to Fix CVE-2026-31836: Access Control Bypass in Checkmate , Access Control Bypass in Checkmate

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 8.2 - High
Actively exploited?	Not currently listed in CISA KEV
Affected	4.5.0 < 4.8.0
Fixed in	See vendor advisory
Type (CWE)	CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

What is CVE-2026-0805?

CVE-2026-0805 is a path traversal flaw in Crafty Controller. The product fails to canonicalize or restrict file paths supplied by a remote caller, so .. sequences or absolute paths reach restricted parts of the filesystem. Vendor description: An input neutralization vulnerability in the Backup Configuration component of Crafty Controller allows a remote, authenticated attacker to perform file tampering and remote code execution via path traversal.

Why this CVE matters

Path traversal flaws look low-impact on paper but routinely chain into full compromise. An attacker who can read arbitrary files often pulls configuration secrets, session databases, or private keys, and many traversal bugs also allow writes that drop a webshell into the document root.

For deployments of Crafty Controller that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Crafty Controller: 4.5.0 < 4.8.0

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open Crafty Controller's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-0805

The fix is to upgrade Crafty Controller to version 4.8.0 or later.

Affected versions confirmed in the CVE record:

Crafty Controller < 4.8.0

Patch via the OS package manager (Linux)


<!-- enrich_agent_2:v1 -->
# 1. Update the package metadata.
sudo apt update                                  # Debian / Ubuntu
sudo dnf check-update                            # RHEL / Rocky / AlmaLinux / Fedora
sudo zypper refresh                              # openSUSE

# 2. Pull the patched version `4.8.0` of Crafty Controller from Arcadia Technology, LLC.
sudo apt install --only-upgrade crafty-controller
sudo dnf upgrade crafty-controller
sudo zypper update crafty-controller

# 3. Restart the affected service so the patched binary is the running binary.
sudo systemctl restart crafty-controller || true

# 4. Verify the running version.
crafty-controller --version

Verify the fix worked


<!-- enrich_agent_2:v1 -->
# 1. Confirm the running version matches the fixed-in version from the advisory.
#    Cross-check against the vendor advisory: https://gitlab.com/crafty-controller/crafty-4/-/issues/650

# 2. Re-scan with your vulnerability scanner. The scanner should no longer flag
#    this CVE on the patched host.
# Example with Nmap NSE:
nmap -sV --script vuln <target-host>

# 3. Inspect the service / kernel logs for crash-loops or rollback events in
#    the first hour after the upgrade.
journalctl -u <service-name> --since "1 hour ago"
dmesg --since "1 hour ago"

If you cannot patch immediately

Block requests containing ../, ..%2f, or absolute path prefixes at a reverse proxy. Restrict access to the affected endpoint to trusted networks. Apply the patched build as the real fix.

How to verify the fix worked

After applying the patch, verify the running version in the product's admin UI or via the vendor-documented CLI command.
Confirm the patched build matches the version listed in the vendor advisory.
Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-0805.
Review logs for the entire pre-patch window for indicators of compromise listed in the vendor or CISA advisory.
Confirm any network-layer mitigations that were applied as a stopgap have been reverted (or left in place intentionally) once the patch is verified.

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unusually long URI paths containing traversal sequences, unexpectedly large responses from the affected endpoint, and outbound requests from the application to internal addresses or cloud-metadata endpoints. Treat any sensitive file the bug could disclose as exposed.

Frequently asked questions

Is CVE-2026-0805 being exploited in the wild?