In 30 seconds

The short version: a researcher is warning that pam-mysql, a Linux login plug-in that checks passwords against a MySQL database, will accept any password at all for SSH accounts that have no stored password. The door everyone assumed was locked turns out to open with any key, if the report holds up.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
The same report says every released version of the module is affected, from Debian and Ubuntu to Fedora and FreeBSD, and rates the flaw, tracked as CVE-2026-124749, at 9.8 out of 10, near the very top of the severity scale.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
What happened
Some background first. The post describes pam-mysql as a login module for Linux that stores account credentials in a MySQL database rather than in the traditional password file. When someone connects over SSH, the server program, sshd, hands the password check to such modules before letting the visitor in.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
The bug, as reported, sits in a single safety check. sshd passes the module a flag that means: refuse accounts with no stored password, and it sets that flag by default. The flaw reverses the logic, so exactly when sshd asks for a rejection, pam-mysql grants access instead, and any password the visitor types will do.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
The finding went public through a post from IntCyberDigest, which credits a researcher, names the CVE as CVE-2026-124749 and quotes the severity at 9.8 out of 10.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
Why it matters
The severity number makes sense given what SSH is: the remote door administrators use to manage servers, so a way in over SSH is usually a way in everywhere. Accounts with no stored password are often left in place precisely because they look inert, since no typed password should ever match them. A bug that admits them with anything converts dormant rows in a database into live entry points.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
The default setting is the part that stings. According to the report, sshd requests rejection of passwordless accounts out of the box, so administrators did nothing unusual to land in the danger zone. Running the module for SSH logins, with passwordless accounts in the backend, is reportedly the whole recipe.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
What to do
The circulating post names no patch, so for now the moves are about shrinking exposure. Find out whether pam-mysql sits in the SSH authentication path at all, since most servers never install it. Where it does run, review which accounts in the MySQL backend have no stored password and treat each one as a potential open door.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
Beyond that, watch the official security channels for Debian, Ubuntu, Fedora and FreeBSD, the systems named in the report, and plan to update the moment patched packages appear. This is advice built from the reported scope, not something the post itself spells out.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
Confirmed and still uncertain
What is claimed, clearly and in detail: the mechanism, a reversed safety flag; the trigger, sshd's default request to reject passwordless accounts; the scope, every released version, with Debian, Ubuntu, Fedora and FreeBSD named; and the paperwork, CVE-2026-124749 rated 9.8 by the researcher.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
What is missing is just as important. The post names no fixed version, no workaround and no evidence of exploitation in the wild, and it cites no vendor confirmation. The unnamed researcher's word, relayed by one account, is currently the whole foundation.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
What people are saying
The only voice on the record is IntCyberDigest, an account on X that published the warning this week and framed it with full urgency: the bug, it says, "lets anyone into SSH accounts that have no stored password, with any password they type." The account attributes both the findings and the 9.8 rating to a researcher it does not name.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
Evolution
This story is at its first beat, the initial disclosure. A CVE identifier with a score already exists, which suggests the finding has been registered somewhere formal, yet the public record here is a single post. The natural next steps are vendor advisories, patched packages and, possibly, debate over whether 9.8 is the right number.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
Reach
1 independent groups, 1 updates, and 13 engagements.
Technical detail
Here is the plumbing, as described. PAM, Pluggable Authentication Modules, is the standard interface Linux and Unix login services use to hand off password checks, and pam-mysql implements it by querying MySQL instead of reading a password file. During an SSH login, sshd calls the module and, by default, passes a flag that forbids accounts with empty or missing passwords. The bug reportedly inverts that flag's meaning, turning an order to reject into permission to admit, so any submitted password passes for such accounts.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
The identifier attached is CVE-2026-124749, and the quoted score, 9.8 out of 10, sits in CVSS critical territory, the band reserved for easily exploited flaws with total impact. The number is the researcher's rating as relayed by the post, not a vendor consensus.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
Sources and evidence
The evidence base is one item: a public post on X from IntCyberDigest, published this week, carrying the researcher's findings alongside a screenshot. It is the sole source for the mechanism, the affected versions, the CVE identifier and the score.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
What would stiffen the story: a vendor advisory, a patch or upstream commit, proof-of-concept details, or a second researcher confirming independently. None of that appears in the batch, so every technical claim above should be read as reported rather than verified.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
Sources
- IntCyberDigestx.com · IntCyberDigest · x



