Lago through 1.55.0 Authentication Bypass via acceptInvite GraphQL Mutation
Lago through 1.55.0 is affected when the invited email already has a Lago account. CVSS rates it 8.7 (high). No fix is listed in the checked facts.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Lago, an open-source billing platform, contains an authentication bypass that lets organization administrators take over existing user accounts without knowing their passwords. An attacker could use this to access the victim's organizations, billing data, API keys, and payment integrations.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- getlago lago
through 1.55.0
References 7
Questions about CVE-2026-119420
What does this mean?
Accepting an invitation with the wrong password can add a membership and issue a JWT for an existing user's account. This lets the invite flow grant access without the correct password.Source: github.com
Am I affected, and how do I check?
Lago through version 1.55.0 is affected, and the bug needs the invited email to already have a Lago account. To check a Lago install, look up its version number and whether the invite targets an existing account.Source: github.com
What should I do about it?
The checked facts name no fixed version. Check the vendor's releases for a version newer than 1.55.0 and install it when available.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data