CVE-2026-55369

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.5 from GitHub Security Advisory (severity: MODERATE) published 2026-10-28. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-112060 (ENISA EUVD) · GHSA-vvx2-3p2j-gx4m (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
6.5MEDIUMhigh confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 28, 2026

Last Modified

November 2, 2026

Advisory Details (3)

Auto-updated Oct 28, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

NoSQL injection in the login endpoint (POST /api/token): a non-string email is silently dropped by the MongoDB storage adapter, producing a match-all filter so the password is verified against the first-registered user (the administrator) — a partial authentication bypass · Advisory · walinejs/waline · GitHub

https://github.com/walinejs/waline/security/advisories/GHSA-jf75-q64q-g65r
GitHub pull request

test(server): replace token logic unit test with /api/token API integration test

Fix merged in walinejs/waline PR #3646 on 2026-06-14 — awaiting tagged release

https://github.com/walinejs/waline/pull/3646
GitHub commit

commit e611aed4e571 (walinejs/waline)

Fix landed in walinejs/waline commit e611aed4e571 — awaiting tagged release

https://github.com/walinejs/waline/commit/e611aed4e571c2a86103f5cee48791ca6b460360

Vendor Advisories for CVE-2026-55369(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@waline/vercel—
  • every version up to 1.41.0: fixed in 1.41.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 19× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  3. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  4. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  6. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  7. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  8. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  9. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-11-02 21:26 UTCEchelonGraph re-scored
  12. 2026-11-02 21:26 UTCGHSA enrichmentGHSA-vvx2-3p2j-gx4m · GitHub severity MODERATE · GitHub CVSS 6.5
  13. 2026-11-02 20:26 UTCEchelonGraph re-scored
  14. 2026-11-02 20:26 UTCGHSA enrichmentGHSA-vvx2-3p2j-gx4m · GitHub severity MODERATE · GitHub CVSS 6.5
  15. 2026-11-02 20:23 UTCEchelonGraph re-scored
  16. 2026-11-02 20:23 UTCGHSA enrichmentGHSA-vvx2-3p2j-gx4m · GitHub severity MODERATE · GitHub CVSS 6.5
  17. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-10-28 14:01 UTCENISA EUVD ID recordedEUVD-2026-112060 · Source: ENISA EUVD
  22. 2026-10-28 13:28 UTCEchelonGraph re-scored
  23. 2026-10-28 13:00 UTCEchelonGraph re-scoredFirst assessed: 6.5 MEDIUM
  24. 2026-10-28 12:59 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55369?
CVE-2026-55369 is a medium-severity vulnerability; its CVE record was published on October 28, 2026. 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…
When was the CVE record for CVE-2026-55369 published?
The CVE record for CVE-2026-55369 was published on October 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 2, 2026; the record at its source may have been updated since.
Is CVE-2026-55369 actively exploited?
CVE-2026-55369 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55369?
CVE-2026-55369 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55369?
A fix for CVE-2026-55369 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55369 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55369

Explore →

Is Your Infrastructure Affected by CVE-2026-55369?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs