{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32733 exists.","fix":"No fix has been published for CVE-2026-32733 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32733 is a high-severity path traversal vulnerability in squidowl halloy, published on 20 Mar 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-32733 and fix it if it is affected.\n\nWhat it is: CVE-2026-32733 is a high-severity path traversal vulnerability in squidowl halloy, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32733 exists.\n\nAffected product: squidowl halloy. 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-32733/ (Markdown: https://insights.sbomify.com/CVE-2026-32733/index.md)","id":"CVE-2026-32733","markdown":"https://insights.sbomify.com/CVE-2026-32733/index.md","name":"CVE-2026-32733","record":{"aliases":["GHSA-fqrv-rfg4-rv89"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_modify","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"IRC client","requires_auth":"none","summary":"Remote attackers can write files outside the save directory via path traversal in DCC transfers, potentially overwriting sensitive files like SSH keys.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"halloy","vendor":"halloy"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Halloy is an IRC application written in Rust. Prior to commit 0f77b2cfc5f822517a256ea5a4b94bad8bfe38b6, the DCC receive flow did not sanitize filenames from incoming `DCC SEND` requests. A remote IRC user could send a filename with path traversal sequences like `../../.ssh/authorized_keys` and the file would be written outside the user's configured `save_directory`. With auto-accept enabled this required zero interaction from the victim. Starting with commit 0f77b2cfc5f822517a256ea5a4b94bad8bfe38b6, all identified code paths sanitize filenames through a shared `sanitize_filename` function.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Halloy has a file transfer path traveral vulnerability","id":"CVE-2026-32733","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"baserCMS: Multiple vulnerabilities in baserCMS","id":"CVE-2026-32734"},"packages":[],"prev":{"headline":"XSS in @leanprover/unicode-input-component","id":"CVE-2026-32732"},"products":["halloy"],"published":"2026-03-20","related":[{"cvss_score":4.8,"headline":"Halloy has insecure file permissions on credential files","id":"CVE-2026-32810","kev_date_added":null,"published":"2026-03-20"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-24","vendors":["squidowl"]},"summary":"Remote attackers can write files outside the save directory via path traversal in DCC transfers, potentially overwriting sensitive files like SSH keys.","url":"https://insights.sbomify.com/CVE-2026-32733/"}