pam-mysql · CVE-2026-124749
pam-mysql bypass
Patch now if…SSH in as users with no stored password. Rare module.
pam-mysql, a rarely used module that checks Linux logins against a MySQL table, gets one check backwards. With sshd's default settings, anyone can log in over SSH as an account whose stored password is empty, typing any password. Debian fixed it on 19 Nov 2026; Ubuntu and Fedora haven't yet. The researcher demonstrated it but hasn't published the exploit, and no attacks are reported.
How scary is it?
Are you affected? only if all are true
1pam-mysql checks your loginscommand
The module is in the PAM setup of a login service such as sshd, the case the researcher tested. Every released version has the bug, 0.8.x and the 1.0.0 betas. Few systems use it: Debian counts 190 installs. A file name in the output means it's in use for that service.1,10
grep -rl pam_mysql /etc/pam.d/2The service refuses empty passwordscommand
That is sshd's default (PermitEmptyPasswords no), and it's what triggers the bug: sshd asks pam-mysql to refuse accounts with no password, and pam-mysql does the opposite. Don't switch it to yes as a fix; the researcher says that opens a different hole. Run as root.1,5
sshd -T | grep -i permitemptypasswords3Some accounts have no passwordcommand
At least one row in the login table has no stored password. On 0.8.x (Debian, Ubuntu, Gentoo, FreeBSD) that means NULL. On the 1.0.0 betas (Fedora, Nix, Mageia, ALT) an empty string counts too, so the common NOT NULL DEFAULT '' column is exposed; the researcher says PostfixAdmin and Froxlor ship tables like that. Replace the table and column names with yours.1
SELECT username FROM users WHERE password IS NULL OR password='';4The package isn't patchedcommand
Fixed: Debian 13 0.8.2-2.1+deb13u1 and Debian 12 0.8.2-2+deb12u1. Some news sites give 0.8.2-2.1 as fixed for Debian 13; Debian lists that version as vulnerable. Not fixed yet on 21 Nov 2026: Debian testing and unstable, Ubuntu ("needs evaluation"), Fedora and Gentoo. On Fedora the package is pam_mysql.2,3,4,8,11,9,12
dpkg -l libpam-mysqlWhat to do
1Update the package
On Debian 12 and 13, install the update from DSA-6643-1 or DLA-4919-1. The fix adds a nullok option, off by default, so accounts with no password are refused. Elsewhere there's no fixed package yet: upstream fixed its 1.0 code on 19 Nov 2026 but hasn't tagged a release, and its 0.8.x branch has no fix.2,3,1,6,7
2No update yet? Fill the gaps
Remove or lock rows with no password in any table used for logins, then make the password column NOT NULL with no empty-string default. That's the researcher's fix for unpatched systems. Don't set PermitEmptyPasswords yes.1
3Check past logins
sshd logs a bypass exactly like a normal login ("Accepted password for"). Any password login by an account that had no stored password at the time was a bypass. The table as it is now may not show what it held then; a backup or the binary log does. pam-mysql's own log table is off by default, and when on it spells failures AUTHENTICATION FALURE.1
This page shows you how to check. It can't tell you you're safe.
Sources (14) and changelog
- oss-security: Andrey Vasilevsky's disclosure, conditions, fix, mitigation, detection 19 Nov
- Debian DSA-6643-1: Debian 13 fixed in 0.8.2-2.1+deb13u1 19 Nov
- Debian DLA-4919-1: Debian 12 fixed in 0.8.2-2+deb12u1, nullok option 19 Nov
- Debian tracker: fixed and vulnerable versions
- OpenSSH source: sshd sets the flag when PermitEmptyPasswords is no
- pam-MySQL upstream: "CVE Fix" commit 19 Nov
- pam-MySQL upstream: "Add nullok option." commit 19 Nov
- Ubuntu: all releases "Needs evaluation"
- Gentoo: bug 986865, confirmed, open 20 Nov
- Debian popcon: 190 libpam-mysql installs
- SecurityOnline: no attacks or public exploit known; gives 0.8.2-2.1 as fixed 21 Nov
- Fedora updates: no pam_mysql security update
- CISA KEV catalog: not listed
- CVE record: not yet published (21 Nov)
- Published.