Waline login accepts a non-string email as a match-all MongoDB query

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-55369: 0.26% estimated exploitation activity in the next 30 days; percentile 18.11 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The login endpoint POST /api/token reads the `email` field from the request body without checking its type and passes it straight into the MongoDB storage query. When `email` is not a string (for example a JSON object such as {"$ne": null}), the MongoDB storage adapter's parseWhere silently DROPS the field rather than rejecting the request, producing an empty filter that matches ALL users. The endpoint then verifies the submitted password against the FIRST user returned (user[0]), which in Waline is the first-registered user — the site administrator. This is a PARTIAL authentication bypass, not a full one. The attacker still needs a valid password for that first user; this is not a zero-knowledge bypass and it does not disclose passwords. Its concrete effects are: (1) the email/identifier factor is removed for the administrator account, (2) user enumeration (a non-string email never fails the "no such user" branch), and (3) credential-stuffing amplification — an attacker…

Published by the source

28 Oct 2026, 21:17 UTC

Last modified by the source

29 Oct 2026, 02:56 UTC

Source last checked

29 Oct 2026, 06:00 UTC

1. Revision 2 · amended · 29 Oct 2026

   Amended from osv record GHSA-jf75-q64q-g65r

2. Revision 1 · created · 28 Oct 2026

   Published from ghsa record GHSA-jf75-q64q-g65r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55369

Advisory: Waline login accepts a non-string email as a match-all MongoDB query
IDs: CVE-2026-55369, GHSA-jf75-q64q-g65r
Record: https://patchnext.com/advisories/ghsa-jf75-q64q-g65r (revision 2, source checked 29 Oct 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @waline/vercel 1.41.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @waline/vercel: affected < 1.41.0; fixed in 1.41.0

## Suggested inspection (read-only)
- `npm ls @waline/vercel --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @waline/vercel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jf75-q64q-g65r (OSV record GHSA-jf75-q64q-g65r lists affected ranges: npm @waline/vercel >=0 <1.41.0 (fixed))
- Verified: https://github.com/advisories/GHSA-jf75-q64q-g65r (GitHub-reviewed advisory GHSA-jf75-q64q-g65r lists affected ranges: npm @waline/vercel >=0 <=1.40.3)

Commands are suggestions: review each one before running it.