CVE-2026-119420: Lago through 1.55.0 Authentication Bypass via acceptInvite GraphQL Mutation
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-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Lago through 1.55.0 contains an authentication bypass vulnerability that allows organization administrators to obtain session tokens for existing accounts via the acceptInvite mutation without a password check. Attackers can invite a victim’s email, accept with an arbitrary password, and receive a JWT to access the victim’s organizations, billing data, API keys and payment integrations.
Description quoted from the CVE record (assigned by VulnCheck, published 2026-10-30).
Weakness: Authentication Bypass Using an Alternate Path or Channel
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: total.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 5 references on Exploit Observer
Live scores
- EPSS
- 0.004
low predicted chance of attack - VEDAS
- 0.987
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| getlago lago | up to and including 1.55.0 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Vendor guidance:
- https://github.com/getlago/lago-api/commit/5a9d5935b027d1db7171c7c015283d5870451305 (patch)
- https://github.com/getlago/lago-api/pull/6146 (issue-tracking, patch)
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-119420 Lago - Authentication Bypass via acceptInvite GraphQL Mutation. 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-119420 Lago - Authentication Bypass via acceptInvite GraphQL Mutation"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/graphql"; nocase; http.request_body; content:"cceptInvite"; nocase; fast_pattern; content:"token"; nocase; distance:0; content:"password"; nocase; classtype:attempted-admin; reference:cve,CVE-2026-119420; reference:url,https://www.exploit.observer/?keyword=CVE-2026-119420&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=lago&match=exact; sid:1105201; rev:1;)
CVE-2026-119420.rules on GitHub
References
Vendor advisories and patches
- https://github.com/getlago/lago-api/commit/5a9d5935b027d1db7171c7c015283d5870451305 (patch)
- https://github.com/getlago/lago-api/pull/6146 (issue-tracking, patch)
Technical analysis and advisories
- https://github.com/getlago/lago-api/blob/v1.55.0/app/services/users_service.rb#L89-L98 (technical-description)
- https://github.com/getlago/lago-api/blob/v1.55.0/app/services/invites/accept_service.rb#L15-L16 (technical-description)
- https://abraxaslabs.tech/research/lago-invite-ato (third-party-advisory)
- VulnCheck Advisory: Lago through 1.55.0 Authentication Bypass via acceptInvite GraphQL Mutation (third-party-advisory)
Other references
- https://github.com/getlago/lago-api (product)
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.