# CVE-2026-130870: ClearFlask before 2.7.3 Improper Authorization via Project Admin Invitation Acceptance


- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-q2q3-44pf-4m3f, GHSA-rgxg-m2g5-vv47

## What is CVE-2026-130870?

CVE-2026-130870 is a critical vulnerability in ClearFlask, published on 17 Nov 2026. 

### Official description

ClearFlask before 2.7.3 contains an improper authorization vulnerability that allows any account holding an invitation ID to accept it regardless of invited email. Attackers who obtain a forwarded or shared invitation link can redeem it via accountAcceptInvitationAdmin or accountSignupAdmin to become project administrators.

Weakness: CWE-863 (Incorrect Authorization)

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

1 open source package ship an affected version, including clearflask/clearflask.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `clearflask/clearflask` | GitHub | `pkg:github/clearflask/clearflask` | All versions | 2.7.3 |

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

Upgrade clearflask/clearflask to 2.7.3 or later.

## Is CVE-2026-130870 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130870 is a critical vulnerability in ClearFlask, published on 17 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130870 exists.

Affected packages and fixed versions:
- clearflask/clearflask (GitHub): affected all versions; fixed in 2.7.3

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

## Sources

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

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