Skip to main content
VulnerabilityPublished

CVE-2026-121582: Umami · Improper Authorization

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-121582· Medium 6.9

Public exploit available · CVSS 6.9 Medium.

Data as of 4 Nov 2026, 02:13 UTC

CVSS 4.0 base score
6.9Medium
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.06.9
CNA (VulDB)CVSS 3.16.5
CNA (VulDB)CVSS 3.06.5
CNA (VulDB)CVSS 2.06.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/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–
GitHubumami-software/umamipkg:github/umami-software/umamiOther threatsAffected
  • =3.4.0
  • =3.4.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should monitor for vendor advisories and updates. Until a patch is released, consider restricting access to the affected API endpoint or implementing additional access controls to mitigate unauthorized use.

Description

A vulnerability in Umami up to version 3.4.1 allows remote attackers to bypass authorization via manipulation of the Website argument in the Record API Endpoint. The flaw affects an unknown function in src/app/api/record/route.ts. Public exploit details have been disclosed, but the vendor has not responded or issued a fix. The vulnerability has a CVSS 3.1 base score of 6.5, indicating medium severity.

References

Community reviews

Loading reviews…