{"answers":{"affected":"3 open source packages ship an affected version, including bugsink. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-40162 in the wild and no public exploit code.","fix":"Upgrade bugsink to 2.1.1 or later.","what":"CVE-2026-40162 is a high-severity vulnerability in bugsink, published on 10 Apr 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-40162 and fix it if it is affected.\n\nWhat it is: CVE-2026-40162 is a high-severity vulnerability in bugsink, published on 10 Apr 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-40162 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- bugsink (PyPI): affected from 2.1.0; fixed in 2.1.1\n- bugsink (PyPI): affected from 2.1.0; fixed in 2.1.1\n- bugsink (PyPI): affected from 2.1.0; fixed in 2.1.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-40162/ (Markdown: https://insights.sbomify.com/CVE-2026-40162/index.md)","id":"CVE-2026-40162","markdown":"https://insights.sbomify.com/CVE-2026-40162/index.md","name":"CVE-2026-40162","record":{"aliases":["GHSA-8hw4-fhww-273g","PYSEC-2026-2404"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Bugsink error tracking","requires_auth":"low_privilege","summary":"Authenticated attackers can write arbitrary files to the server via the artifact bundle assembly flow in Bugsink, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bugsink","vendor":"bugsink"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Bugsink is a self-hosted error tracking tool. In 2.1.0, an authenticated file write vulnerability was identified in Bugsink 2.1.0 in the artifact bundle assembly flow. A user with a valid authentication token could cause the application to write attacker-controlled content to a filesystem location writable by the Bugsink process. This vulnerability is fixed in 2.1.1.","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 affected by authenticated arbitrary file write in artifactbundle/assemble","id":"CVE-2026-40162","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"file_upload","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Saltcorn has an Unauthenticated Path Traversal in sync endpoints allows arbitrary file write and directory read","id":"CVE-2026-40163"},"packages":[{"ecosystem":"PyPI","fixed":["2.1.1"],"introduced":["2.1.0"],"last_affected":[],"package":"bugsink","purl":null,"source":"GHSA-8hw4-fhww-273g"},{"ecosystem":"PyPI","fixed":["2.1.1"],"introduced":["2.1.0"],"last_affected":[],"package":"bugsink","purl":"pkg:pypi/bugsink","source":"GHSA-8hw4-fhww-273g"},{"ecosystem":"PyPI","fixed":["2.1.1"],"introduced":["2.1.0"],"last_affected":[],"package":"bugsink","purl":"pkg:pypi/bugsink","source":"PYSEC-2026-2404"}],"prev":{"headline":"Tekton Pipelines: Git resolver API mode leaks system-configured API token to user-controlled serverURL","id":"CVE-2026-40161"},"products":["bugsink"],"published":"2026-04-10","related":[{"cvss_score":9.3,"headline":"Bugsink is vulnerable to Stored XSS via Pygments fallback in stacktrace rendering","id":"CVE-2026-27614","kev_date_added":null,"published":"2026-02-25"}],"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":"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-04-10","vendors":["bugsink"]},"summary":"Authenticated attackers can write arbitrary files to the server via the artifact bundle assembly flow in Bugsink, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2026-40162/"}