# CVE-2026-72535: Chaskiq Chaskiq - Missing Authentication

> Unauthenticated attackers can mint Stripe Billing Portal sessions for any tenant, allowing unauthorized access and management of subscription data.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-hqqc-4mgp-grm6

## What is CVE-2026-72535?

CVE-2026-72535 is a high-severity missing authorization vulnerability in Chaskiq, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A missing authentication vulnerability in Chaskiq through commit 46dfdd1 allows unauthenticated remote attackers to mint Stripe Billing Portal sessions for any tenant via the stripeCustomerPortal GraphQL mutation. The mutation performs no authentication or authorization checks before creating a customer portal session linked to any tenant Stripe account. An attacker can access and manage subscription data for any tenant without credentials.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-72535 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72535 is a high-severity missing authorization vulnerability in Chaskiq, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72535 in the wild and no public exploit code.

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

## Sources

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

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