IRC in the last 30 days: security releases, new features and what to update (November 2026) | DBase IRC Database

IRC in the last 30 days: security releases, new features and what to update (November 2026)

IRC in the last 30 days: security releases, new features and what to update (November 2026)

IRC in the last 30 days: security releases, new features and what to update (November 2026)

• • 133 回表示

WeeChat shipped three security releases, UnrealIRCd fixed a critical bug, Halloy moved history to SQLite and Libera.Chat switched on bot mode. A round-up of IRC clients, servers and networks from mid-October to mid-November 2026.

IRC in the last 30 days: security releases, new features and what to update (November 2026)

The last 30 days were unusually busy for IRC software. Between mid-October and mid-November 2026, four of the best-known projects shipped security fixes, one of the largest networks switched on new IRCv3 features, and a young Rust client moved its whole message history to SQLite.

This is a round-up of what was released, what changed, and what you should update. Every version and date below was checked against the project's own release notes.

The month at a glance

Date Project Release What it is
17 Oct The Lounge 4.6.0-pre.2 pre-release of the next version
29 Oct mIRC 7.86 fixes, OpenSSL update, per-server IRCv3 settings
31 Oct WeeChat 4.10.2 security release
2 Nov Libera.Chat network update bot mode, bot restrictions, channel context
4 Nov Halloy 2026.10 SQLite history, global search
7 Nov WeeChat 4.10.3 security release
7 Nov UnrealIRCd 6.2.7.1 critical security release and hot-patch
9 Nov WeeChat 4.10.4 security release
14 Nov UnrealIRCd 6.2.8-rc1 release candidate
14 Nov UnrealIRCd webpanel 1.1 and 1.1.1 security release

Two things stand out. Security dominated the month: six of the ten entries include security fixes. And the same IRCv3 features keep appearing in different projects at the same time, which is a good sign that they are becoming part of everyday IRC.

Clients

WeeChat: three security releases in ten days

If you use WeeChat, this is the part to read. Versions 4.10.2, 4.10.3 and 4.10.4 all contain security fixes, and they came out on 31 October, 7 November and 9 November.

4.10.2 (31 October) is the largest. It fixes issues covered by four security advisories:

  • a heap buffer overflow in charset conversion,
  • a heap buffer overflow in nick prefixes when a server sends an empty PREFIX,
  • a heap buffer overflow in the relay "weechat" protocol,
  • an integer overflow in dynamic strings, and unlimited HTTP header size in relay.

It also stops untrusted values from being evaluated: ${ is now escaped in values that come from IRC URLs (irc://...), from channel names saved to autojoin, and in the /allchan, /allpv and /allserv commands.

4.10.3 (7 November) hardens authentication and file transfers:

  • SASL SCRAM now enforces mutual authentication. A login is refused if the server signature was not verified, if the server nonce is wrong, or if the iteration count is below 4096 or above 1,000,000.
  • Relay ignores IRC messages longer than 4096 bytes instead of trying to parse them.
  • DCC: resume positions are validated, and xfer.file.auto_accept_nicks compares the whole server name.
  • Outside security, DCC transfers of files larger than 4 GiB finally work, and several freezes and memory leaks are fixed.

4.10.4 (9 November) closes two more relay issues: a TOTP code must be exactly 6 digits, and only the first password in an init command is checked, so a client can no longer stall WeeChat with many expensive password checks in one message. It also fixes a use-after-free that could crash the raw buffer.

What to do: update to 4.10.4. This matters most if you run the relay plugin, because a relay is a network service that anyone who can reach the port can talk to.

Halloy 2026.10: history in SQLite and a global search

Halloy is an open source IRC client written in Rust, with releases named after the year and month. Version 2026.10 came out on 4 November and is its biggest release of the year.

History and search

  • Message history is now stored in SQLite. Existing gzip history is migrated automatically as you open buffers.
  • Saved history is no longer limited to 10,000 messages per buffer.
  • A new search buffer finds messages across all servers, channels and queries. Open it with /search, from the command bar, the sidebar menu or a nickname's context menu.

Everyday comfort

  • Typing indicators for queries now show in the sidebar.
  • A very long paste can be uploaded to a file host automatically (buffer.text_input.upload_long_paste).
  • Pressing Tab after /topic fills in the current topic so you can edit it.
  • A new title bar button jumps to the backlog divider, the line where you stopped reading.
  • Gopher and Gemini links and IPv6 literal links are clickable.
  • Emoji are updated to Unicode 18.0.

Connection handling

  • Lost connections are detected quickly after you change networks or wake a laptop from sleep. Before, it could take minutes.
  • Reconnect attempts no longer run out while the computer has no network at all.
  • On Windows and macOS, certificates are now verified by the operating system.

One change is worth knowing if you follow IRCv3: Halloy now leaves the no-implicit-names capability off by default and limits how many WHO requests it sends when the capability is on.

mIRC 7.86: fixes and per-server IRCv3 settings

mIRC 7.86 was released on 29 October. It updates OpenSSL to 3.5.9, fixes a bug in the new reply support and lets you turn echo-message, no-implicit-names and server-time on or off for each server. It builds on 7.85 from September, which added WebSocket connections, IRCv3 replies and bans by account.

We covered both versions in detail in mIRC 7.85 and 7.86: WebSockets, IRCv3 replies, account bans and per-server settings.

The Lounge 4.6.0-pre.2

The self-hosted web client published a second pre-release of version 4.6.0 on 17 October. There is no written changelog yet, and the project says features may still change before the first release candidate. It installs only with the next tag, so treat it as a preview. The current stable version is still 4.5.2.

Servers

UnrealIRCd 6.2.7.1: a critical bug, exploited in the wild

On 7 November UnrealIRCd released 6.2.7.1 and a hot-patch that fix nine security issues. The critical one, CVE-2026-114713, lets any ordinary user run commands with server authority, such as KILL and GLINE. The maintainer confirmed a day later that it was being exploited.

If you run UnrealIRCd 6.0.0 to 6.2.7 and have not patched yet, do it now. One command per server, no restart:

./unrealircd hot-patch bundle-20261107

The full story, including the workaround and how to verify the patch, is in UnrealIRCd 6.2.7.1 and 6.2.8-rc1: critical security fix, hot-patch and what is coming next.

UnrealIRCd 6.2.8-rc1

A week later, on 14 November, the first release candidate of 6.2.8 followed. The stable release is expected at the end of November. Three changes need preparation:

  • Browser WebSocket connections are refused unless the origin is listed in set::websocket::allowed-origins.
  • Outgoing server links that use only a password now warn, and become an error in Q1 2027.
  • tkldb stores the source of each ban, so you cannot downgrade without losing it.

UnrealIRCd webpanel 1.1 and 1.1.1

The web admin panel got its first release in two years, and it is a security release. Version 1.1 came out on 14 November, and 1.1.1 followed the same day because 1.1 "went out a bit too early". The project says everyone should upgrade, including from 1.1.

What was fixed:

  • Script injection (XSS): IRC data such as quit messages, realnames, channel names and topics could run as HTML in the panel. The worst case was the Logs page, which any IRC user could reach without a panel account.
  • Forged requests (CSRF): every form and API call now needs a per-session token.
  • Permissions: read-only and limited accounts could use the stored RPC password or start an upgrade. They no longer can.
  • Sessions: a new session ID at login, safer cookies and an idle timeout enforced on the server.
  • Old sample account: the default account with the password testing can no longer log in.

After upgrading, everyone is logged out once. If you serve the panel with nginx, add the rules from the project's doc/webserver-security.md, because the .htaccess protection only works on Apache.

Networks

Libera.Chat: bots get a label, channels get a bot filter

On 2 November Libera.Chat announced a set of features that are live now.

  • Bot user mode +B: marks a client as a bot. The flag shows in WHO and WHOIS, and every message from the bot carries a bot tag. Libera recommends setting it before joining channels.
  • Channel mode +B (restrict bots): bots cannot join unless they match an invite exemption, and bots without voice or op cannot speak. ChanServ is not affected.
  • +channel-context tag: tells a client which channel a private message belongs to. Libera validates the tag and strips it if the sender cannot message that channel.
  • no-implicit-names and labeled-response: both have been available for a while. The post highlights them for client and bot authors.

Still to come, according to the same post:

  • a network icon that clients can fetch (draft/ICON),
  • multiline messages, after more testing,
  • metadata (draft/metadata-3) for display names, nick colours and pronouns,
  • per-channel allowlists for client tags such as +reply and +draft/react, which Libera currently blocks by default.

What connects these releases

The same features, everywhere at once. Libera.Chat now validates +channel-context, and mIRC started routing messages by that tag in September. no-implicit-names shows up in Libera's announcement, in mIRC's per-server settings and in Halloy's changelog in the same few weeks. Server, network and client support are arriving together, which is how an IRCv3 feature becomes usable in practice.

Security work is intense. UnrealIRCd, its webpanel and WeeChat all shipped security releases within two weeks. The UnrealIRCd maintainer says the critical bug was found in an internal audit with the help of AI, and warns that software which has seen no recent security fixes may simply not have been examined yet. Whatever tools are used, the practical lesson is the same: keep IRC software updated, including clients and web panels, and not only the server.

Slightly older, still worth knowing

These came out before the 30-day window, but they are the current versions if you have not updated in a while:

  • Halloy 2026.9 - 1 October 2026
  • InspIRCd 4.12.1 - 26 September 2026
  • soju 0.11.1 (bouncer) - 24 September 2026
  • Anope 2.1.27 (services, development branch) - 15 September 2026
  • ZNC 1.10.3 - 13 September 2026, a security release for CVE-2026-82373
  • mIRC 7.85 - 9 September 2026
  • Eggdrop 1.10.2 - 6 September 2026
  • Ergo 2.19.1 - 5 August 2026

Update checklist

  • WeeChat: update to 4.10.4, especially if you use relay.
  • UnrealIRCd: hot-patch or upgrade to 6.2.7.1, and prepare your config for 6.2.8.
  • UnrealIRCd webpanel: upgrade to 1.1.1.
  • mIRC: update to 7.86.
  • ZNC: make sure you are on 1.10.3.
  • Halloy: 2026.10 is optional but recommended for the connection fixes.

Sources

Related articles

コメント (0)

ログイン to leave a comment

まだコメントはありません。最初のコメントを書きましょう!

投稿を共有

役に立ちましたか?共有しましょう!

Back

Cookie同意

当社は、ブラウジング体験を向上させ、サイトトラフィックを分析し、コンテンツをパーソナライズするためにCookieを使用しています。「同意」をクリックすると、プライバシーポリシーとGDPR規制に従ってCookieの使用に同意したことになります。 プライバシーポリシーについて詳しく見る