Skip to main content
CVE-2026-119548VulnerabilityPublished

Lago through 1.55.0 contains an authorization bypass vulnerability in Invoices::Payments::StripeService that allows

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-119548· Low 2.3

Not known to be exploited · CVSS 2.3 Low.

Data as of 30 Oct 2026, 13:48 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.02.3
CNA (VulnCheck)CVSS 3.13.1
CNACVSS 4.02.3
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
getlagolagoAffected
  • <=1.55.0
Fixed in–
GitHublagopkg:github/lagoOther threatsAffected
  • <=1.55.0
Fixed in–

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

AI-suggested

Until a fix is available, organizations should review and restrict access to their Stripe integration and monitor for suspicious payment_intent.succeeded events that reference invoices outside their organization.

Description

Lago versions through 1.55.0 have an authorization bypass vulnerability in the Invoices::Payments::StripeService component. This flaw allows users from one organization to mark invoices belonging to another organization as paid due to an unscoped invoice lookup. Attackers with control over their organization's Stripe integration can exploit this by signing a payment_intent.succeeded event containing a victim's invoice UUID, enabling unauthorized wallet top-ups or access to payment-gated subscriptions.

References

Community reviews

Loading reviews…