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/20/2026, 23:51:54 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 on Unix-like and macOS platforms prior to commit f180e41061db393acf65bc99f5c5e7397586d9cb create configuration directories and files using default umask settings. Typically, this results in files with permissions set to 0644 and directories to 0755, which are overly permissive for sensitive configuration data. Specifically, the config.toml file and any referenced password files are created with read permissions for all local users. This allows any local user on the system to read plaintext credentials, compromising confidentiality. The vulnerability requires only local access with low privileges, no authentication or user interaction is needed. The patch commit referenced corrects the file and directory permissions to restrict access appropriately, preventing unauthorized local users from reading sensitive configuration files. No known exploits have been reported in the wild, but the risk remains significant in multi-user environments where untrusted users share the same system. The CVSS v4.0 base score is 4.8 (medium), reflecting the local attack vector and limited scope but notable confidentiality impact.

Potential Impact

The primary impact of CVE-2026-32810 is the unauthorized disclosure of plaintext credentials stored in Halloy's configuration files. This can lead to local privilege escalation if credentials are reused or allow attackers to impersonate legitimate users on IRC networks. Organizations running Halloy on multi-user Unix-like or macOS systems are at risk of insider threats or compromised accounts if local users can access these files. While the vulnerability does not allow remote exploitation or direct code execution, the exposure of credentials can facilitate further attacks, including lateral movement or data exfiltration. The impact is particularly critical in environments where Halloy is used for sensitive communications or where local user separation is weak. The lack of user interaction and authentication requirements lowers the barrier for exploitation by any local user, increasing risk in shared systems such as servers, workstations, or development environments.

Mitigation Recommendations

To mitigate CVE-2026-32810, organizations should immediately update Halloy to versions including or later than the commit f180e41061db393acf65bc99f5c5e7397586d9cb, which corrects the file and directory permission assignments. Until patched, administrators should manually restrict permissions on the Halloy configuration directory and files to prevent unauthorized read access, for example by setting config files to 0600 and directories to 0700. Additionally, system administrators should audit local user accounts and limit access to trusted users only, especially on multi-user systems. Employing filesystem access control lists (ACLs) or mandatory access controls (MAC) such as SELinux or AppArmor can further restrict access to sensitive files. Monitoring local access logs and using file integrity monitoring tools can help detect unauthorized access attempts. Finally, educating users about the risks of storing plaintext credentials and encouraging the use of encrypted credential storage or keyrings can 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/20/2026, 11:51:54 PM

Last updated: 3/21/2026, 3:31:19 AM

Views: 9

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