← Back to results
Vulnerability record · public intelligence
CVE-2026-34578
HIGH

OPNsense has an LDAP Injection via Unsanitized Username in Authentication

Published Apr 9, 2026 · Updated Oct 23, 2026

Severity · CVSSHIGH · 8.2
Known exploitationNot listed
EPSS / likelihood0.48%
QFinch risk score10 / 100

Original summary

Normalized public record · Updated Oct 23, 2026

OPNsense has an LDAP Injection via Unsanitized Username in Authentication

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

OPNsense is a FreeBSD based firewall and routing platform. Prior to 26.1.6, OPNsense's LDAP authentication connector passes the login username directly into an LDAP search filter without calling ldap_escape(). An unauthenticated attacker can inject LDAP filter metacharacters into the username field of the WebGUI login page to enumerate valid LDAP usernames in the configured directory. When the LDAP server configuration includes an Extended Query to restrict login to members of a specific group, the same injection can be used to bypass that group membership restriction and authenticate as any LDAP user whose password is known, regardless of group membership. This vulnerability is fixed in 26.1.6.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
MEDIUM
Confidence
10%
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗

Record history

Published Apr 9, 2026 · Last refreshed Oct 23, 2026