# CVE-2026-55739: Crater - Missing Tenant-Ownership Check in CustomerPolicy Allows Cross-Company Customer Data Theft and Deletion

> Attackers can access and delete customer data across different companies due to missing tenant-ownership checks in the CustomerPolicy.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-j2xj-x8wc-f6xg

## What is CVE-2026-55739?

CVE-2026-55739 is a high-severity missing authorization vulnerability in crater-invoice Crater, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Crater isolates data per company_id, and its Invoice/Estimate/Payment/Expense policies enforce both a Bouncer ability check and ->hasCompany(->company_id). CustomerPolicy's view/update/delete methods omit the company-ownership check entirely, checking only the blanket ability. Route-model-bound customer lookups and the bulk Customer::deleteCustomers method are similarly unscoped (self::find with no company filter).

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-55739 being exploited?

There is no known exploitation of CVE-2026-55739 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55739 is a high-severity missing authorization vulnerability in crater-invoice Crater, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-55739 in the wild and no public exploit code.

Affected product: crater-invoice Crater. 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-55739/ (Markdown: https://insights.sbomify.com/CVE-2026-55739/index.md)
```

## Sources

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

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