Loading vulnerability…
Rodauth versions before 2.46.0 contain an improper authentication flaw in the webauthn_login route. Account-resolution logic can fall back to account identifiers held in the current session instead of validating that the WebAuthn credential is bound to the account being authenticated. This permits an authenticated user to complete WebAuthn authentication in the context of another account.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability tracked as CVE-2026-82466 affecting the Debian Linux 14.0/ruby-rodauth configuration identified by the plugin. The supplied CVSS vectors indicate network exposure and potential high confidentiality and integrity impact, but no availability impact under CVSS v3/v4.
An authentication-bypass vulnerability in Rodauth versions before 2.46.0. Improper account-resolution logic in the webauthn_login route can fall back to session account identifiers rather than validating credential binding, allowing an authenticated user to impersonate arbitrary accounts.
An authentication-bypass vulnerability in Rodauth versions before 2.46.0. Improper account-resolution logic in the webauthn_login route can fall back to session account identifiers rather than validating credential binding, allowing logged-in users to authenticate as arbitrary accounts.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.