{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34578 exists.","fix":"No fix has been published for CVE-2026-34578 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34578 is a high-severity vulnerability in opnsense core, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34578 and fix it if it is affected.\n\nWhat it is: CVE-2026-34578 is a high-severity vulnerability in opnsense core, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34578 exists.\n\nAffected product: opnsense core. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-34578/ (Markdown: https://insights.sbomify.com/CVE-2026-34578/index.md)","id":"CVE-2026-34578","markdown":"https://insights.sbomify.com/CVE-2026-34578/index.md","name":"CVE-2026-34578","record":{"aliases":["GHSA-jpm7-f59c-mp54"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OPNsense firewall","requires_auth":"none","summary":"Unauthenticated attackers can inject LDAP filters to enumerate users or bypass group restrictions in OPNsense firewall authentication.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"opnsense","vendor":"opnsense"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-90","name":"Improper Neutralization of Special Elements used in an LDAP Query"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"OPNsense has an LDAP Injection via Unsanitized Username in Authentication","id":"CVE-2026-34578","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"MantisBT has an authorization bypass via private issue monitoring","id":"CVE-2026-34579"},"packages":[],"prev":{"headline":"Postiz: Unauthenticated Full-Read SSRF via /public/stream Endpoint with Trivially Bypassable Extension Check","id":"CVE-2026-34577"},"products":["core"],"published":"2026-04-09","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2023-27152","kev_date_added":null,"published":"2023-10-23"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-39001","kev_date_added":null,"published":"2023-08-09"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2023-39004","kev_date_added":null,"published":"2023-08-09"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-39008","kev_date_added":null,"published":"2023-08-09"},{"cvss_score":9.6,"headline":"Cross-site scripting in n/a","id":"CVE-2023-39007","kev_date_added":null,"published":"2023-08-09"},{"cvss_score":9.1,"headline":"OPNsense: RCE via XMLRPC endpoint using `opnsense.restore_config_section` method","id":"CVE-2026-44193","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":9.1,"headline":"OPNsense: RCE on user managment","id":"CVE-2026-44194","kev_date_added":null,"published":"2026-05-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-09","vendors":["opnsense"]},"summary":"Unauthenticated attackers can inject LDAP filters to enumerate users or bypass group restrictions in OPNsense firewall authentication.","url":"https://insights.sbomify.com/CVE-2026-34578/"}