{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25742 exists.","fix":"No fix has been published for CVE-2026-25742 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25742 is a medium-severity missing authorization vulnerability in zulip, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25742 and fix it if it is affected.\n\nWhat it is: CVE-2026-25742 is a medium-severity missing authorization vulnerability in zulip, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25742 exists.\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-25742/ (Markdown: https://insights.sbomify.com/CVE-2026-25742/index.md)","id":"CVE-2026-25742","markdown":"https://insights.sbomify.com/CVE-2026-25742/index.md","name":"CVE-2026-25742","record":{"aliases":["GHSA-f47p-xjqq-g28w"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Zulip collaboration tool","requires_auth":"none","summary":"Attackers can anonymously access files and topic history from web-public streams even after disabling spectator access, exposing sensitive data.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zulip","vendor":"zulip"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Zulip is an open-source team collaboration tool. Prior to version 11.6, Zulip is an open-source team collaboration tool. From version 1.4.0 to before version 11.6, even after spectator access (enable_spectator_access / WEB_PUBLIC_STREAMS_ENABLED) is disabled, attachments originating from web-public streams can still be retrieved anonymously. As a result, file contents remain accessible even after public access is intended to be disabled. Similarly, even after spectator access is disabled, the /users/me/\u003cstream_id\u003e/topics endpoint remains reachable anonymously, allowing retrieval of topic history for web-public streams. This issue has been patched in version 11.6. This issue has been patched in version 11.6.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Zulip: Anonymous File Access After Disabling Spectator Access","id":"CVE-2026-25742","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"OpenEMR has Stored XSS in Questionnaire answers","id":"CVE-2026-25743"},"packages":[],"prev":{"headline":"Zulip Vulnerable to Modification of Payment Method (Stripe Default Card) by Non-Billing Users","id":"CVE-2026-25741"},"products":["zulip"],"published":"2026-04-03","related":[{"cvss_score":8.6,"headline":"RabbitMQ exposes ports with weak default secrets in Zulip Server","id":"CVE-2021-43799","kev_date_added":null,"published":"2022-01-25"},{"cvss_score":8,"headline":"Crafted link in Zulip message can cause disclosure of credentials","id":"CVE-2022-35962","kev_date_added":null,"published":"2022-08-29"},{"cvss_score":7.5,"headline":"Auth bypass in zulip","id":"CVE-2016-4427","kev_date_added":null,"published":"2022-07-28"},{"cvss_score":6.8,"headline":"Cross-site Scripting (XSS) - Stored in zulip/zulip","id":"CVE-2021-3866","kev_date_added":null,"published":"2022-01-20"},{"cvss_score":6.5,"headline":"Unauthorized user can register an account in specific configurations in Zulip","id":"CVE-2023-28623","kev_date_added":null,"published":"2023-05-19"},{"cvss_score":6.5,"headline":"Ineffective expiration validation for invitation links in Zulip","id":"CVE-2021-43791","kev_date_added":null,"published":"2021-12-02"},{"cvss_score":6.1,"headline":"Zulip: Path Traversal in Import","id":"CVE-2026-26058","kev_date_added":null,"published":"2026-04-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["zulip"]},"summary":"Attackers can anonymously access files and topic history from web-public streams even after disabling spectator access, exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-25742/"}