Security incident · CVE-2026-55369
Waline login accepts a non-string email as a match-all MongoDB query
Published Oct 28, 2026 · catalog updated Oct 29, 2026 · Waline login accepts a
Last checked Oct 29, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-55369. EPSS is 0.26%. Act only if a listed version of Waline login accepts a is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Waline login accepts a).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium6.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.26%
- Remediation
- Advisory link
- Affected products
- npm @waline/vercel
## Summary The login endpoint POST /api/token reads the field from the request body without checking its type and passes it straight into the MongoDB storage query. When 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 can test a leaked or weak password against the administrator account without knowing the administrator's email. ## Details Untyped input — packages/server/src/controller/token.js:17-18: email filter email email email password` as strings before they reach the storage query — for example in packages/server/src/logic/token.js postAction(): Defense in depth: in mongodb.js parseWhere(), reject (rather than silently drop) a value that is neither a string nor a supported array form, or coerce it to {$eq: String(value)}, so a non-string key can never elide the filter.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- npm @waline/vercel0 → 1.41.0
How to fix CVE-2026-55369
Upgrade
CVE-2026-55369 lists a fix boundary at 1.41.0. Compare the installed build with that boundary before you change production.
Version check
Fixed in 1.41.0
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-55369. EPSS is 0.26%. Act only if a listed version of Waline login accepts a is installed.
Which versions are affected?
Compare what you have installed with 0 → 1.41.0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-287: Improper Authentication; CWE-943. EPSS 0.26%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 28, 2026 · GitHub Advisory Database
Detected
## Summary The login endpoint POST /api/token reads the field from the request body without checking its type and passes it straight into the MongoDB storage query. When 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
Oct 29, 2026 · GitHub Advisory Database
Fix available
@waline/vercel fixed in 1.41.0
Oct 29, 2026 · GitHub Advisory Database
Fix available
@waline/vercel fixed in 1.41.0
Oct 29, 2026 · GitHub Advisory Database
Updated
## Summary The login endpoint POST /api/token reads the field from the request body without checking its type and passes it straight into the MongoDB storage query. When 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
Sources
- CVE.orgVulnerability recordCVE-2026-55369
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-55369
30-day exploitation probability 0.26%
first.org - GitHub Advisory DatabasePackage advisoryGHSA-jf75-q64q-g65r
GitHub Advisory Database record mirrored by OSV.
github.com - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-jf75-q64q-g65r
Waline login accepts a non-string email as a match-all MongoDB query
osv.dev
References
Freshness
Last verified in this catalog Oct 29, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- CVE.orgOct 29, 2026
- FIRST EPSSOct 29, 2026
- GitHub Advisory DatabaseOct 29, 2026
- OpenSSF OSV / OSV ScannerOct 29, 2026