Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-32810: CWE-732: Incorrect Permission Assignment for Critical Resource in squidowl halloy

0
Medium
VulnerabilityCVE-2026-32810cvecve-2026-32810cwe-732
Published: Fri Mar 20 2026 (03/20/2026, 22:40:49 UTC)
Source: CVE Database V5
Vendor/Project: squidowl
Product: halloy

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/28/2026, 21:27:24 UTC

Technical Analysis

CVE-2026-32810 is a vulnerability classified under CWE-732 (Incorrect Permission Assignment for Critical Resource) affecting the Halloy IRC client developed by squidowl. Halloy versions up to 2026.4 on Unix-like and macOS platforms create configuration directories and files using default system umask permissions. Typically, this results in files having permissions of 0644 and directories 0755, which are overly permissive for sensitive configuration data. Specifically, the config.toml file and any password files referenced within it are stored in plaintext and are readable by any local user on the system. This exposure allows unauthorized local users to access plaintext credentials, potentially leading to unauthorized access or impersonation within IRC networks or other services relying on these credentials. The vulnerability does not require elevated privileges or user interaction to exploit but does require local access to the system. The issue was addressed in commit f180e41061db393acf65bc99f5c5e7397586d9cb, which presumably enforces stricter file permissions to protect sensitive files. No known exploits are reported in the wild as of the publication date. The CVSS 4.0 vector indicates low attack complexity, local attack vector, low confidentiality impact, and no impact on integrity or availability.

Potential Impact

The primary impact of CVE-2026-32810 is the unauthorized disclosure of plaintext credentials stored in Halloy's configuration files. For organizations, this can lead to several risks: unauthorized access to IRC accounts or networks, potential lateral movement if credentials are reused, and exposure of sensitive communication channels. Since the vulnerability requires local access, it poses a significant risk in multi-user environments such as shared servers, development workstations, or any system where multiple users have shell access. Attackers with local access but without elevated privileges can exploit this to escalate their access or gather intelligence. While the vulnerability does not directly compromise system integrity or availability, the confidentiality breach can facilitate further attacks or data exfiltration. Organizations relying on Halloy for internal or external communications should consider the risk of credential leakage and potential downstream impacts on their security posture.

Mitigation Recommendations

To mitigate CVE-2026-32810, organizations should immediately update Halloy to versions including or beyond the patch commit f180e41061db393acf65bc99f5c5e7397586d9cb. If immediate updating is not feasible, administrators should manually adjust file and directory permissions for Halloy's configuration files to restrict access to the owning user only (e.g., chmod 600 for files and chmod 700 for directories). Additionally, auditing local user accounts and limiting shell access to trusted personnel reduces the risk of exploitation. Employing filesystem access control mechanisms such as SELinux or AppArmor profiles can further restrict unauthorized reads. Organizations should also consider encrypting sensitive configuration data or using secure credential storage mechanisms rather than plaintext files. Regularly monitoring file permissions and access logs for anomalies can help detect attempts to exploit this vulnerability. Finally, educating users about the risks of local access and enforcing strong local user account policies will reduce exposure.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-16T17:35:36.696Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69bdda59b462d409683a8cc3

Added to database: 3/20/2026, 11:38:01 PM

Last enriched: 3/28/2026, 9:27:24 PM

Last updated: 5/2/2026, 2:59:52 PM

Views: 76

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses