{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32810 exists.","fix":"No fix has been published for CVE-2026-32810 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32810 is a medium-severity vulnerability in squidowl halloy, published on 20 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-32810 and fix it if it is affected.\n\nWhat it is: CVE-2026-32810 is a medium-severity vulnerability in squidowl halloy, published on 20 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32810 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-32810/ (Markdown: https://insights.sbomify.com/CVE-2026-32810/index.md)","id":"CVE-2026-32810","markdown":"https://insights.sbomify.com/CVE-2026-32810/index.md","name":"CVE-2026-32810","record":{"aliases":["GHSA-x5j2-fr4h-9p7g"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IRC client","requires_auth":"low_privilege","summary":"Local attackers can read plaintext credentials from Halloy IRC client config files due to insecure default file permissions.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"halloy","vendor":"halloy"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"Halloy is an IRC application written in Rust. In versions on \\*nix and macOS prior to commit f180e41061db393acf65bc99f5c5e7397586d9cb, halloy creates its config directory and files using default umask permissions, which typically results in `0644` on files and `0755` on directories. This allows any local user on the system to read plaintext credentials stored in `config.toml` or referenced `password_file` paths. Commit f180e41061db393acf65bc99f5c5e7397586d9cb patches the issue.","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 insecure file permissions on credential files","id":"CVE-2026-32810","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Heimdall: Path received via Envoy gRPC corrupted when containing query string","id":"CVE-2026-32811"},"packages":[],"prev":{"headline":"pyLoad: Arbitrary File Deletion via Path Traversal during Encrypted 7z Password Verification","id":"CVE-2026-32808"},"products":["halloy"],"published":"2026-03-20","related":[{"cvss_score":8.7,"headline":"Halloy has a file transfer path traveral vulnerability","id":"CVE-2026-32733","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-23","vendors":["squidowl"]},"summary":"Local attackers can read plaintext credentials from Halloy IRC client config files due to insecure default file permissions.","url":"https://insights.sbomify.com/CVE-2026-32810/"}