CVE-2026-55369VulnerabilityPublished 28 Oct 2026

waline · Prior to version 1.41.1, the login endpoint POST /api/token reads the email field from the request body without

Affects walineSource GCVE Database

Authoritative record:CVE-2026-55369· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.41.1 when convenient.

Data as of 28 Oct 2026, 16:30 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 1.41.1

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-vvx2-3p2j-gx4m

What to do

Upgrade waline to 1.41.1.

Affected software

Product	Affected	Fixed in
npmwaline`pkg:npm/waline`Other threats	Affected <1.41.1	Fixed in 1.41.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Waline to version 1.41.1 or later, where this issue has been patched. The patch ensures proper type checking of the email field before using it in MongoDB queries, preventing the bypass. No additional mitigation steps are required once the update is applied.

Description

Waline versions prior to 1.41.1 have a partial authentication bypass vulnerability in the login endpoint POST /api/token. The endpoint reads the email field from the request body without validating its type and passes it directly into a MongoDB query. If the email is a non-string JSON object, the query filter becomes empty and matches all users, causing the system to verify the password against the first user (the administrator). This allows attackers to bypass the email check for the administrator account, enabling user enumeration and credential-stuffing amplification. The issue is patched in version 1.41.1.

Impact

The vulnerability allows attackers to bypass the email verification step for the administrator account during login, effectively removing the email factor. This enables user enumeration since non-string emails do not trigger a 'no such user' response. It also amplifies credential-stuffing attacks by allowing attackers to test passwords against the administrator account without knowing the administrator's email. However, attackers still need a valid password for the administrator account, so it is a partial authentication bypass with limited impact on confidentiality and no impact on availability.

CWE-287Improper Authentication (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Libraries or Frameworks
Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Fake the Source of Data (opens in a new tab)
Utilizing REST's Trust in the System Resource to Obtain Sensitive Data (opens in a new tab)
Session Hijacking (opens in a new tab)
Token Impersonation (opens in a new tab)
Upload a Web Shell to a Web Server (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 16:30 UTC

WeaknessesCWE-287

Technical details

References

Community reviews

Related threats