{"answers":{"affected":"1 open source package ship an affected version, including discourse.","exploited":"There is no known exploitation of CVE-2026-72723 in the wild and no public exploit code.","fix":"Upgrade discourse to a fixed version for your release line: 2026.1.6, 2026.5.2 or 2026.6.1.","what":"CVE-2026-72723 is a medium-severity vulnerability in discourse, published on 10 Aug 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-72723 and fix it if it is affected.\n\nWhat it is: CVE-2026-72723 is a medium-severity vulnerability in discourse, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-72723 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- discourse (Bitnami): affected all versions; fixed in 2026.1.6, 2026.5.2, 2026.6.1\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-72723/ (Markdown: https://insights.sbomify.com/CVE-2026-72723/index.md)","id":"CVE-2026-72723","markdown":"https://insights.sbomify.com/CVE-2026-72723/index.md","name":"CVE-2026-72723","record":{"aliases":["BIT-discourse-2026-72723","GHSA-4p6q-h74v-5j7p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Discourse forum","requires_auth":"none","summary":"Unauthenticated attackers can view restricted tag names and descriptions via the site JSON endpoint, exposing category-restricted metadata.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"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":"Discourse is an open-source discussion platform. Prior to 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0, SiteSerializer.anonymous_default_navigation_menu_tags serializes tags from SiteSetting.default_navigation_menu_tags without applying DiscourseTagging.filter_visible for the anonymous viewer. An unauthenticated user can retrieve restricted tag names and descriptions through /site.json when those tags are limited by inaccessible categories, category tag groups, or tag-group permissions. This issue is fixed in versions 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Discourse: Anonymous sidebar serialization exposes descriptions of category-restricted tags","id":"CVE-2026-72723","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":1,"n_references":9,"next":{"headline":"Discourse: Private Chat Threat Message Disclosure via Chat Onebox Channel/Threat ID Mismatch","id":"CVE-2026-72724"},"packages":[{"ecosystem":"Bitnami","fixed":["2026.1.6","2026.5.2","2026.6.1"],"introduced":["0","2026.5.0","2026.6.0"],"last_affected":[],"package":"discourse","purl":"pkg:bitnami/discourse","source":"BIT-discourse-2026-72723"}],"prev":{"headline":"Discourse: Duplicate lookup reveals restricted topic titles through canonicalized URLs","id":"CVE-2026-72722"},"products":["discourse"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-10","vendors":["discourse"]},"summary":"Unauthenticated attackers can view restricted tag names and descriptions via the site JSON endpoint, exposing category-restricted metadata.","url":"https://insights.sbomify.com/CVE-2026-72723/"}