CVE-2026-55377

{"id": "CVE-2026-55377", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-55377", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-07-13T16:20:33.380860Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.1, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 2.8}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "logto-io", "product": "logto", "versions": [{"status": "affected", "version": "< 1.41.0"}]}]}], "published": "2026-07-10T20:16:46.460", "references": [{"url": "https://github.com/logto-io/logto/commit/f56255a7edf3b22b0ec2fdb814814ce6b0123b74", "source": "security-advisories@github.com"}, {"url": "https://github.com/logto-io/logto/pull/9110", "source": "security-advisories@github.com"}, {"url": "https://github.com/logto-io/logto/releases/tag/v1.41.0", "source": "security-advisories@github.com"}, {"url": "https://github.com/logto-io/logto/security/advisories/GHSA-q4h3-38gc-4p4j", "source": "security-advisories@github.com"}, {"url": "https://github.com/logto-io/logto/security/advisories/GHSA-q4h3-38gc-4p4j", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-287"}]}], "descriptions": [{"lang": "en", "value": "Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto's Account Center step-up check accepted any active verification record that belonged to the current user and had isVerified === true. A WebAuthn registration verification record for binding a new passkey could be created and verified with only an existing Account API bearer token, then sent in the logto-verification-id header and treated as identityVerified=true by Account Center routes, allowing MFA factor management without proving possession of an existing password, identifier, or MFA factor. This issue is fixed in version 1.41.0."}], "lastModified": "2026-07-13T19:21:55.683", "sourceIdentifier": "security-advisories@github.com"}