{"answers":{"affected":"3 open source packages ship an affected version, including bugsink.","exploited":"There is no known exploitation of CVE-2026-47715 in the wild and no public exploit code.","fix":"Upgrade bugsink to 2.2.0 or later.","what":"CVE-2026-47715 is a low-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-47715 and fix it if it is affected.\n\nWhat it is: CVE-2026-47715 is a low-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-47715 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-47715/ (Markdown: https://insights.sbomify.com/CVE-2026-47715/index.md)","id":"CVE-2026-47715","markdown":"https://insights.sbomify.com/CVE-2026-47715/index.md","name":"CVE-2026-47715","record":{"aliases":["GHSA-vx2f-6m6h-9frf","PYSEC-2026-2407"],"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":"Logged-in users can view event data from other projects by manipulating event identifiers in URLs, exposing sensitive stack traces and details.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Bugsink is a self-hosted error tracking tool. Prior to 2.2.0, Bugsink issue event pages accept a direct event identifier from the URL and, in affected versions, look up that event without also requiring it to belong to the issue in the URL. This is a project-boundary authorization issue: a logged-in user with access to one project can view another project’s event data through an issue they are allowed to access. The affected views include the stacktrace, details, and breadcrumbs pages for an issue event. 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: Issue event views can show an event from another project if its UUID is known","id":"CVE-2026-47715","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":"Bugsink: Issue bulk actions can affect another project’s issue if its UUID is known","id":"CVE-2026-47716"},"packages":[{"ecosystem":"PyPI","fixed":["2.2.0"],"introduced":["0"],"last_affected":[],"package":"bugsink","purl":null,"source":"GHSA-vx2f-6m6h-9frf"},{"ecosystem":"PyPI","fixed":["2.2.0"],"introduced":["0"],"last_affected":[],"package":"bugsink","purl":"pkg:pypi/bugsink","source":"GHSA-vx2f-6m6h-9frf"},{"ecosystem":"PyPI","fixed":["2.2.0"],"introduced":["0"],"last_affected":[],"package":"bugsink","purl":"pkg:pypi/bugsink","source":"PYSEC-2026-2407"}],"prev":{"headline":"libheif has integer overflow in inline mask size calculation that causes undersized buffer allocation","id":"CVE-2026-47714"},"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-28","vendors":["bugsink"]},"summary":"Logged-in users can view event data from other projects by manipulating event identifiers in URLs, exposing sensitive stack traces and details.","url":"https://insights.sbomify.com/CVE-2026-47715/"}