---
id: "CVE-2026-119548"
kind: "vulnerability"
aliases: ["CVE-2026-119548"]
title: "Lago: billing flaw lets one organization mark another's invoice paid"
severity: "low"
cvss: 3.1
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["billing", "lago", "other", "self-hosted", "stripe"]
not_affected_if: ["no-stripe-integration", "single-organization"]
published_at: "2026-10-30T12:16:41+00:00"
first_seen_at: "2026-10-30T12:30:26+00:00"
updated_at: "2026-10-30T12:34:12+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119548", "first_seen_at": "2026-10-30T12:30:26+00:00"}]
---

# Lago: billing flaw lets one organization mark another's invoice paid

Lago, an open-source billing platform, looks up invoices in its Stripe payment handler without scoping them to the caller's organization. An attacker running their own Stripe integration can send a signed payment success event naming another organization's invoice, marking it paid and unlocking wallet top-ups or subscriptions.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Lago version against the affected range (through `1.55.0`).
- Look for the Stripe payment handling in `Invoices::Payments::StripeService` in your Lago deployment.

## Timeline

- 2026-10-30T12:30:26+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-119548

## From the sources

Lago through 1.55.0 contains an authorization bypass vulnerability in Invoices::Payments::StripeService that allows users of one organization to mark another organization's invoice as paid due to an unscoped invoice lookup. Attackers controlling their organization's Stripe integration can sign a payment_intent.succeeded event carrying a victim invoice UUID to unlock wallet top-ups or payment-gated subscriptions.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_