{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-25741 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-25741 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-25741 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-25741 in the wild and no public exploit code.\n\nAffected product: zulip. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-25741/ (Markdown: https://insights.sbomify.com/CVE-2026-25741/index.md)","id":"CVE-2026-25741","markdown":"https://insights.sbomify.com/CVE-2026-25741/index.md","name":"CVE-2026-25741","record":{"aliases":["GHSA-vhhx-84f7-rc8j"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Zulip team collaboration","requires_auth":"low_privilege","summary":"Non-billing users can modify the organization's default payment method due to missing authorization checks in the upgrade flow API.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Zulip Vulnerable to Modification of Payment Method (Stripe Default Card) by Non-Billing Users","id":"CVE-2026-25741","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Zulip: Anonymous File Access After Disabling Spectator Access","id":"CVE-2026-25742"},"packages":[],"prev":{"headline":"Privilege escalation to the `CAP_NET_RAW` capability via the `programs.captive-browser` NixOS module","id":"CVE-2026-25740"},"products":["zulip"],"published":"2026-02-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-03","vendors":["zulip"]},"summary":"Non-billing users can modify the organization's default payment method due to missing authorization checks in the upgrade flow API.","url":"https://insights.sbomify.com/CVE-2026-25741/"}