# CVE-2026-78807: Auth bypass in n/a > Local attackers can bypass network context and AKMP matching for PMKSA caching in wpa_supplicant due to missing validation in the driver-based selection path. - **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 11 Sep 2026 - **Updated:** 11 Sep 2026 - **Also known as:** AZL-103386, DEBIAN-CVE-2026-78807, GHSA-3gc7-g84m-84jc, SUSE-SU-2026:24096-1, SUSE-SU-2026:24132-1, SUSE-SU-2026:24144-1, SUSE-SU-2026:24278-1, SUSE-SU-2026:4494-1, SUSE-SU-2026:4587-1, SUSE-SU-2026:4588-1, SUSE-SU-2026:4590-1, UBUNTU-CVE-2026-78807, openSUSE-SU-2026:22022-1 ## What is CVE-2026-78807? CVE-2026-78807 is a high-severity authentication bypass vulnerability in n/a, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description An issue in wpa_supplicant all versions before v.2.12 allows a local attacker to bypass proper network context and AKMP matching for PMKSA caching via missing validation in the driver based PMKSA selection path in wpa.c Weakness: CWE-346 (Origin Validation Error) ## Which versions are affected by CVE-2026-78807? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `wpa_supplicant` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 2.9-150000.4.45.1 | | `wpa_supplicant` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 2.9-150000.4.45.1 | | `wpa_supplicant` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 2.10-150500.3.9.1 | | `wpa_supplicant` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 2.10-150500.3.9.1 | | `wpa_supplicant` | SUSE:Linux Enterprise Micro 5.3 | All versions | 2.9-150000.4.45.1 | | `wpa_supplicant` | SUSE:Linux Enterprise Micro 5.4 | All versions | 2.9-150000.4.45.1 | | `wpa_supplicant` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.10-150500.3.9.1 | | `wpa_supplicant` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 2.11-150700.3.6.1 | | `wpa_supplicant` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 2.9-23.26.1 | | `wpa_supplicant` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 2.9-150000.4.45.1 | | `wpa_supplicant` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 2.10-150500.3.9.1 | | `wpa_supplicant` | SUSE:Linux Enterprise Server 16.0 | All versions | 2.11-160000.5.1 | | `wpa_supplicant` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.9-23.26.1 | | `wpa_supplicant` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 2.9-150000.4.45.1 | | `wpa_supplicant` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 2.10-150500.3.9.1 | | `wpa_supplicant` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 2.11-160000.5.1 | | `wpa_supplicant` | SUSE:Linux Micro 6.0 | All versions | 2.10-159998.1.1 | | `wpa_supplicant` | SUSE:Linux Micro 6.1 | All versions | 2.11-slfo.1.1_3.1 | | `wpa_supplicant` | SUSE:Linux Micro 6.2 | All versions | 2.11-160000.5.1 | | `wpa_supplicant` | openSUSE:Leap 16.0 | All versions | 2.11-160000.5.1 | ## How do I fix CVE-2026-78807? Upgrade to a fixed version. ## Is CVE-2026-78807 being exploited? There is no known exploitation of CVE-2026-78807 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-78807 and fix it if it is affected. What it is: CVE-2026-78807 is a high-severity authentication bypass vulnerability in n/a, published on 11 Sep 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-78807 in the wild and no public exploit code. Affected product: n/a. 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-78807/ (Markdown: https://insights.sbomify.com/CVE-2026-78807/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-78807 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-78807 - OSV: https://osv.dev/vulnerability/CVE-2026-78807 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-78807/ Summaries are generated and may contain mistakes; the official description above is the record.