CVE-2026-124749: Authentication bypass in pam-MySQL through inverted PAM_DISALLOW_NULL_AUTHTOK handling
CVE-2026-124749 is an authentication bypass affecting pre-fix releases of pam-MySQL, also packaged as libpam-mysql. Both authentication call sites in pam_sm_authenticate invert PAM_DISALLOW_NULL_AUTHTOK when passing the null_inhibited argument, enabling credential-less authentication precisely when the calling application requests its rejection. For affected database records, password comparison is skipped and an arbitrary supplied password can succeed. The 0.8.x line is exploitable with SQL NULL stored passwords; the 1.0 line additionally treats empty stored passwords as eligible for the vulnerable branch. OpenSSH's default PermitEmptyPasswords=no setting triggers the defective flag handling when vulnerable pam-MySQL is used for authentication.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
An unauthenticated attacker can impersonate an account whose database password meets the vulnerable condition, gaining access to services and resources authorized for that account. Confidentiality, integrity, and availability consequences depend on the account's privileges and the exposed service; privileged affected accounts could permit extensive compromise. Accounts with real stored passwords are not subject to this specific bypass. Controlled exploitation has been demonstrated, but exploitation in the wild is not confirmed.
Mitigation
If you can’t patch tonight, do this now.
Until patched, remove credential-less records from authentication tables or assign valid, nonempty password credentials so those records cannot authenticate through the vulnerable branch. Enforce NOT NULL on password columns without an empty-string default, and separately prevent empty stored passwords, particularly on the 1.0 line; NOT NULL alone does not prevent its empty-password bypass. Do not enable OpenSSH PermitEmptyPasswords as a workaround, because doing so removes OpenSSH's own empty-password protection. For retrospective investigation, correlate successful logins with historical SQL NULL or empty-password records using database backups or binary logs; ordinary OpenSSH success messages do not distinguish bypasses from legitimate authentication.
Remediation
Patch, then assume compromise.
Upgrade Debian stable (trixie) pam-mysql to 0.8.2-2.1+deb13u1 or a later vendor-fixed package. For other distributions, install an update incorporating both the authentication flag-polarity correction and the default-off nullok option. The combined upstream fix corrects both authentication call sites and permits credential-less authentication only when nullok is explicitly enabled and PAM_DISALLOW_NULL_AUTHTOK is not set. Upstream committed the combined fix on November 19, 2026; at disclosure, no new upstream release was tagged and the upstream 0.8.x branch remained unfixed. Avoid incomplete patches: a polarity-only correction changes behavior for callers passing flags=0, and routing empty passwords into the vulnerable branch without correcting polarity introduces an additional bypass.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-124749 exploited in the wild?
- As of Nov 20, 2026, Mallory has no reports of CVE-2026-124749 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-124749?
- As of Nov 20, 2026, Mallory has found no public exploit for CVE-2026-124749.
- Is there a patch for CVE-2026-124749?
- Upgrade Debian stable (trixie) pam-mysql to 0.8.2-2.1+deb13u1 or a later vendor-fixed package. For other distributions, install an update incorporating both the authentication flag-polarity correction and the default-off nullok option.
Recent activity
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.