# CVE-2026-33432: Roxy-WI has Pre-Authentication LDAP Injection that Leads to Authentication Bypass

> Unauthenticated attackers can bypass authentication in Roxy-WI via LDAP injection when LDAP is enabled, gaining unauthorized access to the management interface.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** GHSA-hv3x-4w38-r92m

## What is CVE-2026-33432?

CVE-2026-33432 is a high-severity authentication bypass vulnerability in roxy-wi, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers. In versions up to and including 8.2.8.2, when LDAP authentication is enabled, Roxy-WI constructs an LDAP search filter by directly concatenating the user-supplied login username into the filter string without escaping LDAP special characters. An unauthenticated attacker can inject LDAP filter metacharacters into the username field to manipulate the search query, cause the directory to return an unintended user entry, and bypass authentication entirely — gaining access to the application without knowing any valid password. As of time of publication, no known patches are available.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Roxy-Wi Roxy-Wi.

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

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

## Is CVE-2026-33432 being exploited?

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

## Other vulnerabilities in roxy-wi

- [CVE-2022-31161](https://insights.sbomify.com/CVE-2022-31161/): Roxy-WI Vulnerable to Unauthenticated Remote Code Execution via ssl_cert Upload (critical 10.0)
- [CVE-2022-31137](https://insights.sbomify.com/CVE-2022-31137/): Unauthenticated Remote Code Execution in Roxy-WI (critical 10.0)
- [CVE-2022-31125](https://insights.sbomify.com/CVE-2022-31125/): Authentication Bypass in Roxy-wi (critical 10.0)
- [CVE-2022-31126](https://insights.sbomify.com/CVE-2022-31126/): Unauthenticated Remote Code Execution in Roxy-wi (critical 10.0)
- [CVE-2021-38167](https://insights.sbomify.com/CVE-2021-38167/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33432 is a high-severity authentication bypass vulnerability in roxy-wi, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33432 in the wild and no public exploit code.

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

## Sources

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

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