# CVE-2026-45255: Remote code execution via installer Wi-Fi access point scans

> Attackers can execute arbitrary commands as root by broadcasting a malicious Wi-Fi network name during FreeBSD installer scans.

- **Severity:** High 7.5 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2026
- **Updated:** 22 May 2026
- **Also known as:** GHSA-qj4f-cpgw-vqx9

## What is CVE-2026-45255?

CVE-2026-45255 is a high-severity command injection vulnerability in Freebsd Freebsd, published on 21 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

When bsdinstall or bsdconfig are prompted to scan for nearby Wi-Fi networks, they build up a list of network names and use bsddialog(1) to prompt the user to select a network.  This is implemented using a shell script, and the code which handled network names was not careful to prevent expansion by the shell.  As a result, a suitably crafted network name can be used to execute commands via a subshell.

The problem can be exploited to execute code as root on the system running bsdinstall or bsdconfig.  The attacker would need to create an access point with a specially crafted name and be within range of a Wi-Fi scan.  Note that bsdinstall and bsdconfig are vulnerable as soon as the user prompts them to scan for nearby networks; they do not need to actually select the malicious network.

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

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

It affects 1 product.


Products: Freebsd Freebsd.

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

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

## Is CVE-2026-45255 being exploited?

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

## Other vulnerabilities in Freebsd Freebsd

- [CVE-2018-17160](https://insights.sbomify.com/CVE-2018-17160/): Memory corruption in FreeBSD (critical 10.0)
- [CVE-2014-3954](https://insights.sbomify.com/CVE-2014-3954/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-4304](https://insights.sbomify.com/CVE-2006-4304/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-0226](https://insights.sbomify.com/CVE-2006-0226/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0002](https://insights.sbomify.com/CVE-2004-0002/): Denial of service in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45255 is a high-severity command injection vulnerability in Freebsd Freebsd, published on 21 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-45255 in the wild and no public exploit code.

Affected product: Freebsd Freebsd. 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-45255/ (Markdown: https://insights.sbomify.com/CVE-2026-45255/index.md)
```

## Sources

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

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