{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-40300 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-40300 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-40300 is a medium-severity vulnerability in zulip, published on 12 May 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-40300 and fix it if it is affected.\n\nWhat it is: CVE-2026-40300 is a medium-severity vulnerability in zulip, published on 12 May 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-40300 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-40300/ (Markdown: https://insights.sbomify.com/CVE-2026-40300/index.md)","id":"CVE-2026-40300","markdown":"https://insights.sbomify.com/CVE-2026-40300/index.md","name":"CVE-2026-40300","record":{"aliases":["GHSA-jp8f-mvv6-89cr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Zulip team collaboration","requires_auth":"low_privilege","summary":"Low-privilege users can recover edited message content via API despite restrictive visibility policies, exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zulip_server","vendor":"zulip"}],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"Zulip is an open-source team collaboration tool. Prior to 12.0, With message_edit_history_visibility_policy set to \"moves\", /api/v1/messages/{id}/history still returns historical content values, allowing low-privilege users to recover text that was edited away from other users' messages. This vulnerability is fixed in 12.0.","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: Message edit history visible in \"moves only\" policy through /api/v1/messages/{id}/history","id":"CVE-2026-40300","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"rhukster/dom-sanitizer: SVG \u003cstyle\u003e tag allows CSS injection via unfiltered url() and @import directives","id":"CVE-2026-40301"},"packages":[],"prev":{"headline":"next-intl has an open redirect vulnerability","id":"CVE-2026-40299"},"products":["zulip"],"published":"2026-05-12","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2019-18933","kev_date_added":null,"published":"2019-11-21"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2020-15070","kev_date_added":null,"published":"2020-08-21"},{"cvss_score":8.8,"headline":"Missing authorization in Zulip Server","id":"CVE-2017-0910","kev_date_added":null,"published":"2017-11-27"},{"cvss_score":8.2,"headline":"Zulip Authentication Backend Configuration Bypass","id":"CVE-2025-31478","kev_date_added":null,"published":"2025-04-16"},{"cvss_score":8.2,"headline":"Cross-site scripting vulnerability in Zulip Server development branch via topic tooltip","id":"CVE-2023-33186","kev_date_added":null,"published":"2023-05-30"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-36612","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":7.5,"headline":"Privilege escalation in n/a","id":"CVE-2020-14215","kev_date_added":null,"published":"2020-08-21"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-13","vendors":["zulip"]},"summary":"Low-privilege users can recover edited message content via API despite restrictive visibility policies, exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-40300/"}