CVE-2026-55369: Waline login accepts a non-string email as a match-all MongoDB query
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Waline is a comment system with backend support. Prior to version 1.41.1, 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 can test a leaked or weak password against the administrator account without knowing the administrator’s email. This issue has been patched in version 1.41.1.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-10-28).
Weakness: CWE-287: Improper Authentication; CWE-943: Improper Neutralization of Special Elements in Data Query Logic
How it can be exploited
Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality low, integrity low, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Public exploit evidence (Exploit Observer)
Also known as: GHSA-vvx2-3p2j-gx4m
VEDAS cluster: VEDAS:DOVEROAM
Exploit Observer links 3 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (3)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-55369.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-55369.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-55369.rules
Vulnerability databases and vendor advisories (2)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-vvx2-3p2j-gx4m
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-55369
3 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.003
low predicted chance of attack - VEDAS
- 0.988
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| walinejs waline | version <= 1.40.3 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-55369 Waline - NoSQL Operator Injection Authentication Bypass. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-55369 Waline - NoSQL Operator Injection Authentication Bypass"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/token"; nocase; fast_pattern; http.request_body; content:"|22|email|22|:{|22|$"; classtype:web-application-attack; reference:cve,CVE-2026-55369; reference:url,https://www.exploit.observer/?keyword=CVE-2026-55369&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=waline&match=exact; sid:1089600; rev:1;)
CVE-2026-55369.rules on GitHub
References
Other references
- https://github.com/walinejs/waline/security/advisories/GHSA-jf75-q64q-g65r (x_refsource_CONFIRM)
- https://github.com/walinejs/waline/pull/3646 (x_refsource_MISC)
- https://github.com/walinejs/waline/commit/e611aed4e571c2a86103f5cee48791ca6b460360 (x_refsource_MISC)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.