CVE-2026-46649

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 56% 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 week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: None knownExposed: 0

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

Joplin is an open source note-taking and to-do application that organises notes and lists into notebooks. Prior to 3.7.2, Joplin Server's GET /api/login_with_code/:id endpoint accepts a nine-digit SSO authentication code with a ten-minute lifetime without applying limiterLoginBruteForce. An unauthenticated attacker who targets a user during an active SSO login can make unlimited guesses, and a correct code returns a full session token that permits access to and modification of the user's notes, notebooks, and account settings. This issue is fixed in version 3.7.2.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

September 21, 2026

Last Modified

September 23, 2026

Advisory Details (4)

Auto-updated Sep 21, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit.
generic

GitHub - laurent22/joplin at v3.7.2 · GitHub

https://github.com/laurent22/joplin/tree/v3.7.2
github_commit

commit fd8c1fb53f98 (laurent22/joplin)

Fix landed in laurent22/joplin commit fd8c1fb53f98 — awaiting tagged release

https://github.com/laurent22/joplin/commit/fd8c1fb53f98f689e846dc164e39f307f09b684d
github_pr

Server: Add rate limiter on SAML auth code endpoint

Fix merged in laurent22/joplin PR #15433 on 2026-05-15 — awaiting tagged release

https://github.com/laurent22/joplin/pull/15433
github Patch Available🟡 PoC Available

SSO Auth Code Login Missing Rate Limiting — 9-Digit Numeric Code Brute-Forceable via Unprotected Endpoint · Advisory · laurent22/joplin · GitHub

https://github.com/laurent22/joplin/security/advisories/GHSA-6vwc-4hrg-qp5h

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 7× 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-09-24 15:52 UTCEG score recompute
  2. 2026-09-23 18:39 UTCEG score recompute
  3. 2026-09-23 17:53 UTCEPSS rescore
  4. 2026-09-22 18:17 UTCEG score recompute
  5. 2026-09-21 21:22 UTCEG score recompute
  6. 2026-09-21 21:02 UTCEG score recompute
  7. 2026-09-21 21:01 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46649?
CVE-2026-46649 is a critical vulnerability published on September 21, 2026. Joplin is an open source note-taking and to-do application that organises notes and lists into notebooks. Prior to 3.7.2, Joplin Server's GET /api/loginwithcode/:id endpoint accepts a nine-digit SSO authentication code with a ten-minute lifetime without applying limiterLoginBruteForce. An…
When was CVE-2026-46649 disclosed?
CVE-2026-46649 was first published in the National Vulnerability Database on September 21, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46649 actively exploited?
CVE-2026-46649 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 55.7% of all scored CVEs.
What is the CVSS score of CVE-2026-46649?
CVE-2026-46649 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-46649?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46649, 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-46649

Explore →

Is Your Infrastructure Affected by CVE-2026-46649?

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

Book a Demo →Browse All CVEs