# CVE-2026-119420: Lago through 1.55.0 Authentication Bypass via acceptInvite GraphQL Mutation


- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-gvqv-g6vj-p22g

## What is CVE-2026-119420?

CVE-2026-119420 is a high-severity vulnerability in getlago lago, published on 30 Oct 2026. 

### Official 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.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2026-119420?


## How do I fix CVE-2026-119420?

No fix has been published for CVE-2026-119420 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119420 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119420 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119420 and fix it if it is affected.

What it is: CVE-2026-119420 is a high-severity vulnerability in getlago lago, published on 30 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119420 exists.

Affected product: getlago lago. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119420/ (Markdown: https://insights.sbomify.com/CVE-2026-119420/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119420
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119420
- OSV: https://osv.dev/vulnerability/CVE-2026-119420

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119420/
Summaries are generated and may contain mistakes; the official description above is the record.