Skip to main content
VulnerabilityPublished

CVE-2026-121531: Umami 3.3.x/3.4.0/3.4.1 · Improper Authentication

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-121531· Medium 5.3

Public exploit available · CVSS 5.3 Medium.

Data as of 4 Nov 2026, 02:28 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulDB)CVSS 4.05.3
CNA (VulDB)CVSS 3.16.3
CNA (VulDB)CVSS 3.06.3
CNA (VulDB)CVSS 2.06.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
UmamiAffected
  • =3.4.0
  • =3.4.1
Fixed in–

AI-suggested

Users should consider disabling affected versions or implementing additional compensating controls to mitigate the risk until a patch is released. Monitor vendor channels for updates.

Description

A vulnerability in Umami versions 3.3.x, 3.4.0, and 3.4.1 affects the 2FA Policy Handler component, specifically in the file src/app/api/auth/login/route.ts. This flaw allows an attacker to bypass two-factor authentication, effectively reducing the authentication to single-factor. The vulnerability can be exploited remotely. Public exploit details have been disclosed, but the vendor has not responded or issued a fix.

References

Community reviews

Loading reviews…