# Fider: Cross-Tenant Authentication Bypass via Missing tenant_id Filter in getVerificationByKey

CVE record · `CVE-2026-65840`

- **Identifiers:** `CVE-2026-65840`
- **State:** Confirmed
- **Severity:** CVSS 9.6 Critical
- **Critical:** Yes: CVSS 9+
- **CNA:** GitHub_M
- **Weakness (CWE):** [CWE-639](https://cwe.mitre.org/data/definitions/639.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Technologies:** [fider](https://agentprime.io/advisories/technology/fider.md)
- **Published:** 11 Nov 2026
- **Updated:** 12 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: GitHub_M) at 11 Nov 2026, 18:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Critical

Critical, because:

- CVSS score 9.6: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected products, as the CNA wrote them

- Vendor: getfider. Product: fider.
  - affected: `< 0.36.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Fider versions before 0.36.0 are vulnerable when running in multi-tenant mode (HOST_MODE=multi). An attacker who holds an email verification key issued on one tenant can use it on another tenant to sign in as the same email address, bypassing tenant isolation and taking over the account there. Single-host deployments (the default) are not affected. Upgrade to version 0.36.0 or later.

Written 20 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 9.6 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0030, the 22nd percentile, on 22 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 11 Nov 2026, 18:32 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-65840)
- 11 Nov 2026, 18:41 UTC: First seen by agentprime
- 11 Nov 2026, 19:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-65840)

## Sources

- [CVE List: CVE-2026-65840](https://www.cve.org/CVERecord?id=CVE-2026-65840)
- [NVD: CVE-2026-65840](https://nvd.nist.gov/vuln/detail/CVE-2026-65840)

### References from the CNA

- <https://github.com/getfider/fider/security/advisories/GHSA-vxjw-gv4f-vq58> (confirm)
- <https://github.com/getfider/fider/releases/tag/v0.36.0>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-65840>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-65840/>. Everything for agents: <https://agentprime.io/llms.txt>.
