# CVE-2026-16751: Ente Museum Server Authorization Bypass Vulnerability

> An authenticated attacker acting as an emergency contact can bypass recovery waiting periods to take over victim accounts via a crafted API request.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-jmh3-fv99-c329

## What is CVE-2026-16751?

CVE-2026-16751 is a medium-severity authentication bypass vulnerability in Ente Museum Server, published on 29 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Authorization Bypass in the emergency recovery approval component in Ente Technologies Ente Museum Server allows an authenticated attacker configured as a victim's emergency contact to bypass the configured recovery waiting period and take over the victim's account via a crafted `approve-recovery` API request.

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


## How do I fix CVE-2026-16751?

No fix has been published for CVE-2026-16751 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16751 being exploited?

There is no known exploitation of CVE-2026-16751 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16751 and fix it if it is affected.

What it is: CVE-2026-16751 is a medium-severity authentication bypass vulnerability in Ente Museum Server, published on 29 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16751 in the wild and no public exploit code.

Affected product: Ente Museum Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16751/ (Markdown: https://insights.sbomify.com/CVE-2026-16751/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16751
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16751
- OSV: https://osv.dev/vulnerability/CVE-2026-16751

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16751/
Summaries are generated and may contain mistakes; the official description above is the record.