{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-25195 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-25195 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25195 is a medium-severity vulnerability in zulip, published on 13 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-25195 and fix it if it is affected.\n\nWhat it is: CVE-2025-25195 is a medium-severity vulnerability in zulip, published on 13 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-25195 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-2025-25195/ (Markdown: https://insights.sbomify.com/CVE-2025-25195/index.md)","id":"CVE-2025-25195","markdown":"https://insights.sbomify.com/CVE-2025-25195/index.md","name":"CVE-2025-25195","record":{"aliases":["GHSA-x8cx-3hq5-4wj9"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Zulip team chat","requires_auth":"low_privilege","summary":"An attacker can view private channel names via leaked events, exposing sensitive organizational structure to unauthorized users.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Zulip is an open source team chat application. A weekly cron job (added in 50256f48314250978f521ef439cafa704e056539) demotes channels to being \"inactive\" after they have not received traffic for 180 days.  However, upon doing so, an event was sent to all users in the organization, not just users in the channel.  This event contained the name of the private channel. Similarly, the same commit (50256f48314250978f521ef439cafa704e056539) added functionality to notify clients when channels stopped being \"inactive.\"  The first message sent to a private channel which had not previously had any messages for over 180 days (and were thus already marked \"inactive\") would leak an event to all users in the organization; this event also contained the name of the private channel. Commits 75be449d456d29fef27e9d1828bafa30174284b4 and a2a1a7f8d152296c8966f1380872c0ac69e5c87e fixed the issue. This vulnerability only existed in `main`, and was not part of any published versions.","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 events can leak private channel names","id":"CVE-2025-25195","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"OpenFGA Authorization Bypass","id":"CVE-2025-25196"},"packages":[],"prev":{"headline":"Server-Side Request Forgery (SSRF) in activitypub_federation","id":"CVE-2025-25194"},"products":["zulip"],"published":"2025-02-13","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":"2025-02-14","vendors":["zulip"]},"summary":"An attacker can view private channel names via leaked events, exposing sensitive organizational structure to unauthorized users.","url":"https://insights.sbomify.com/CVE-2025-25195/"}