# Waline login accepts a non-string email as a match-all MongoDB query Advisory record · `GHSA-jf75-q64q-g65r` - **Identifiers:** `GHSA-jf75-q64q-g65r` · `CVE-2026-55369` - **State:** Confirmed - **Severity:** CVSS 6.5 Medium - **Critical:** No - **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html) · [CWE-943](https://cwe.mitre.org/data/definitions/943.html) - **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [Other injection](https://agentprime.io/advisories/tag/injection.md) - **Published:** 28 Oct 2026 - **Updated:** 29 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 28 Oct 2026, 21:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `@waline/vercel` (npm): affected `<1.41.0`; fixed in `1.41.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Waline's @waline/vercel package is affected in versions before 1.41.0. The login endpoint accepts a non-string email value, which the MongoDB storage adapter silently drops from the query, so the lookup matches all users and checks the submitted password against the first-registered user, typically the site administrator. An unauthenticated attacker who sends such a request can enumerate users and test passwords against the administrator account without knowing its email, and gains administrator login if the password is valid. Upgrade to @waline/vercel 1.41.0 or later. Written 31 Oct 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0026, the 18th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 28 Oct 2026, 12:56 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-55369) - 28 Oct 2026, 13:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-55369) - 31 Oct 2026, 13:32 UTC: First seen by agentprime - 31 Oct 2026, 13:32 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jf75-q64q-g65r) ## Sources - [GitHub Advisory Database: GHSA-jf75-q64q-g65r](https://github.com/advisories/GHSA-jf75-q64q-g65r) - [OSV: GHSA-jf75-q64q-g65r](https://osv.dev/vulnerability/GHSA-jf75-q64q-g65r) - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .