CVE-2026-55377

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
17.4%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 13, 2026

Advisory Details (4)

Auto-updated Jul 10, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

Account Center MFA management step-up bypass via WebAuthn registration verification · Advisory · logto-io/logto · GitHub

https://github.com/logto-io/logto/security/advisories/GHSA-q4h3-38gc-4p4j
github_release Patch Available

v1.41.0

Patch available: logto-io/logto v1.41.0

https://github.com/logto-io/logto/releases/tag/v1.41.0
github_pr Patch Available

fix(core): restrict account center step-up verification

Patch available: logto-io/logto v1.41.0 (PR #9110 merged 2026-06-30)

https://github.com/logto-io/logto/pull/9110
github_commit Patch Available

commit f56255a7edf3 (logto-io/logto)

Patch available: logto-io/logto v1.41.0 (contains commit f56255a7edf3)

https://github.com/logto-io/logto/commit/f56255a7edf3b22b0ec2fdb814814ce6b0123b74

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:31 UTCEG score recompute
  4. 2026-07-15 03:35 UTCEG score recompute
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-14 14:38 UTCEG score recompute
  8. 2026-07-14 01:42 UTCEG score recompute
  9. 2026-07-13 22:31 UTCEPSS rescore
  10. 2026-07-13 12:44 UTCEG score recompute
  11. 2026-07-13 06:13 UTCEPSS rescore
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-12 23:48 UTCEG score recompute
  14. 2026-07-12 10:52 UTCEG score recompute
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-11 21:56 UTCEG score recompute
  17. 2026-07-11 09:00 UTCEG score recompute
  18. 2026-07-10 20:04 UTCEG score recompute
  19. 2026-07-10 20:02 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55377?
CVE-2026-55377 is a high vulnerability published on July 10, 2026. 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…
When was CVE-2026-55377 disclosed?
CVE-2026-55377 was first published in the National Vulnerability Database on July 10, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55377 actively exploited?
CVE-2026-55377 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55377?
CVE-2026-55377 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-55377?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55377, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55377

Explore →

Is Your Infrastructure Affected by CVE-2026-55377?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs