{"answers":{"affected":"3 open source packages ship an affected version, including bugsink.","exploited":"There is no known exploitation of CVE-2026-47728 in the wild and no public exploit code.","fix":"Upgrade bugsink to 2.2.0 or later.","what":"CVE-2026-47728 is a medium-severity missing authorization vulnerability in bugsink, published on 26 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-47728 and fix it if it is affected.\n\nWhat it is: CVE-2026-47728 is a medium-severity missing authorization vulnerability in bugsink, published on 26 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-47728 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- bugsink (PyPI): affected all versions; fixed in 2.2.0\n- bugsink (PyPI): affected all versions; fixed in 2.2.0\n- bugsink (PyPI): affected all versions; fixed in 2.2.0\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-47728/ (Markdown: https://insights.sbomify.com/CVE-2026-47728/index.md)","id":"CVE-2026-47728","markdown":"https://insights.sbomify.com/CVE-2026-47728/index.md","name":"CVE-2026-47728","record":{"aliases":["GHSA-5389-f7vh-wxj8","PYSEC-2026-2402"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Bugsink error tracking","requires_auth":"low_privilege","summary":"Authenticated users can access sourcemap and debug-file metadata from other projects due to missing project scoping in lookup logic.","user_interaction":"not_required","vuln_class":"missing_authorization"},"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-862","name":"Missing Authorization"}],"description":"Bugsink is a self-hosted error tracking tool. Prior to 2.2.0, Bugsink resolved sourcemaps and debug files by debug ID without scoping that lookup to the project that owned the uploaded metadata. An authenticated user with access to one project could cause event processing in that project to use sourcemap/debug-file metadata uploaded for another project in the same Bugsink instance, if the same debug ID was referenced. This vulnerability is fixed in 2.2.0.","ecosystems":["PyPI"],"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":"Bugsink: Project scoping missing in sourcemap and debug-file lookup","id":"CVE-2026-47728","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Squid: Memory disclosure in FTP gateway","id":"CVE-2026-47729"},"packages":[{"ecosystem":"PyPI","fixed":["2.2.0"],"introduced":["0"],"last_affected":[],"package":"bugsink","purl":null,"source":"GHSA-5389-f7vh-wxj8"},{"ecosystem":"PyPI","fixed":["2.2.0"],"introduced":["0"],"last_affected":[],"package":"bugsink","purl":"pkg:pypi/bugsink","source":"GHSA-5389-f7vh-wxj8"},{"ecosystem":"PyPI","fixed":["2.2.0"],"introduced":["0"],"last_affected":[],"package":"bugsink","purl":"pkg:pypi/bugsink","source":"PYSEC-2026-2402"}],"prev":{"headline":"Code injection in Trilium","id":"CVE-2026-47727"},"products":["bugsink"],"published":"2026-05-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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-26","vendors":["bugsink"]},"summary":"Authenticated users can access sourcemap and debug-file metadata from other projects due to missing project scoping in lookup logic.","url":"https://insights.sbomify.com/CVE-2026-47728/"}