# CVE-2026-25741: Zulip Vulnerable to Modification of Payment Method (Stripe Default Card) by Non-Billing Users

> Non-billing users can modify the organization's default payment method due to missing authorization checks in the upgrade flow API.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:** 26 Feb 2026
- **Updated:** 3 Mar 2026
- **Also known as:** GHSA-vhhx-84f7-rc8j

## What is CVE-2026-25741?

CVE-2026-25741 is a high-severity missing authorization vulnerability in zulip, published on 26 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Zulip is an open-source team collaboration tool. Prior to commit bf28c82dc9b1f630fa8e9106358771b20a0040f7, the API endpoint for creating a card update session during an upgrade flow was accessible to users with only organization member privileges. When the associated Stripe Checkout session is completed, the Stripe webhook updates the organization’s default payment method. Because no billing-specific authorization check is enforced, a regular (non-billing) member can change the organization’s payment method. This vulnerability affected the Zulip Cloud payment processing system, and has been patched as of commit bf28c82dc9b1f630fa8e9106358771b20a0040f7. Self-hosted deploys are no longer affected and no patch or upgrade is required for them.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-25741 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25741 is a high-severity missing authorization vulnerability in zulip, published on 26 Feb 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-25741 in the wild and no public exploit code.

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

## Sources

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

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