Loading vulnerability…
CVE-2026-55377 is an improper authentication flaw in Logto affecting versions prior to 1.41.0. The vulnerability exists in the Account Center step-up verification logic, which accepted any active verification record associated with the current user when that record was marked as verified. Because a WebAuthn registration verification record used for binding a new passkey could be created and successfully verified using only an existing Account API bearer token, an attacker could supply that verification record in the verification header and have Account Center routes treat the session as identity-verified. This allowed step-up authentication to be bypassed during sensitive account operations, specifically MFA factor management, without demonstrating possession of an existing password, identifier, or enrolled MFA factor.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.