# CVE-2026-71242: Crater - Cross-Company IDOR on Notes via Missing Company-Ownership Check in NotePolicy

> Authenticated users can access, edit, or delete notes from other companies due to missing ownership checks in the NotePolicy.

- **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-2467-45mc-2xp5

## What is CVE-2026-71242?

CVE-2026-71242 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's NotePolicy checks only a blanket Bouncer ability (manage-all-notes / view-all-notes) with no company-ownership comparison, unlike InvoicePolicy and other sibling policies which additionally verify ->hasCompany(->company_id). Any authenticated user of one company can read, edit, or delete another company's notes by ID.

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

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


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

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

## Is CVE-2026-71242 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71242 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-71242 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-71242/ (Markdown: https://insights.sbomify.com/CVE-2026-71242/index.md)
```

## Sources

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

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