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

> Local attackers can read plaintext credentials from Halloy IRC client config files due to insecure default file permissions.

- **Severity:** Medium 4.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-x5j2-fr4h-9p7g

## What is CVE-2026-32810?

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.

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

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2026-32810?

It affects 1 product.


Products: Halloy Halloy.

## How do I fix CVE-2026-32810?

No fix has been published for CVE-2026-32810 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-32810 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32810 exists.

## Other vulnerabilities in squidowl halloy

- [CVE-2026-32733](https://insights.sbomify.com/CVE-2026-32733/): Halloy has a file transfer path traveral vulnerability (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32810 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32810 exists.

Affected product: squidowl halloy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32810/ (Markdown: https://insights.sbomify.com/CVE-2026-32810/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32810
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32810
- OSV: https://osv.dev/vulnerability/CVE-2026-32810

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32810/
Summaries are generated and may contain mistakes; the official description above is the record.