Skip to main content

Solanum IRCd CVE-2026-121603

| EUVDEUVD-2026-116038 HIGH
Classic Buffer Overflow (CWE-120)
2026-11-03 VulnCheck
8.5
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Operate rogue or compromised linked peer server
  2. Exploit
    Send server-to-server KILL with overlong reason
  3. Execution
    Overflow static 512-byte buffer in ms_kill()
  4. Impact
    Crash ircd or potentially achieve code execution

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Buffer copy size validation
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to control a linked peer server in the Solanum IRC network - a rogue server or a compromised legitimate peer that already holds an established, trusted server-to-server link; it is NOT reachable by ordinary clients or by unauthenticated outside attackers. The malicious peer triggers the flaw by sending a KILL message handled by ms_kill() with a reason string whose length exceeds KILLLEN, overflowing a static 512-byte buffer. Limiting factors: server linking in IRC is a privileged, pre-configured trust relationship (link blocks/credentials), so realistic risk is confined to networks that federate with partially-trusted or externally-operated servers; affected builds are those before commit 2ea1382, and updating past that commit removes the flaw by truncating the reason.

Impact

This is a genuine but access-gated server-to-server vulnerability, not an internet-facing mass-exploitation risk. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:N, score 8.5) correctly captures the most important limiter via PR:H: exploitation requires the attacker to control a linked peer in the IRC server mesh, meaning a rogue or already-compromised server that has an established, trusted server-to-server link - not an ordinary client and not an unauthenticated remote attacker. Given that gate, attack complexity is low and the overflow is reliably triggerable by any peer that can emit a KILL. No EPSS score, no CISA KEV listing, and no PoC/exploit reference are present in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the only confirmed artifacts are the vendor patch (PR #550 / commit 2ea1382). The vuln.today priority is 'this_week' rather than act_now/emergency, which is consistent with a high-impact bug whose exploitation precondition (holding a trusted link) substantially narrows the realistic attacker set. One signal conflict worth noting: the supplied CVSS 4.0 vector sets VA:N (no availability impact) even though the description explicitly states the overflow crashes the ircd - the availability impact appears understated. Net: treat as a priority patch for operators running multi-server IRC networks, especially networks that federate links with partially-trusted or externally-operated servers, but it is not a drop-everything internet-wide emergency.

Exploit ScenarioDerived

An attacker who operates a rogue server linked into a Solanum-based IRC network - or who has compromised a legitimately linked peer - sends a KILL command through the server-to-server protocol with a reason string longer than KILLLEN. The oversized reason overflows a static 512-byte buffer in the ms_kill() handler, crashing the target ircd and potentially allowing remote code execution. No public PoC or exploit code is referenced in the available data; only the fixing patch is published.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 03, 2026

Memory corruption in Solanum IRCd's server-to-server KILL handler (ms_kill) lets an attacker who controls a linked peer server crash the ircd and potentially execute code by sending a kill reason longer than KILLLEN, which overflows a static 512-byte buffer. Only builds prior to commit 2ea1382 are affected, and the flaw is not reachable by ordinary IRC clients - the attacker must already hold an established, trusted server-to-server link (the CVSS 4.0 vector rates PR:H for this reason). A vendor patch exists via PR #550 / commit 2ea1382, and no public exploit code was identified at the time of analysis.

RemediationAI

Update to a Solanum build that includes commit 2ea1382e4262b212a91034258c466f0f6754cd61 (merged via PR https://github.com/solanum-ircd/solanum/pull/550), which adds a KILLLEN length check that truncates overlong kill reasons before they reach the static buffer; no tagged release version is stated in the available data, so verify the deployed build contains that commit rather than relying on a version string. Because exploitation requires an established server link, the effective interim control is to restrict federation to peers you actually trust: audit and prune link blocks, remove or disable links to externally operated or partially trusted servers, and require strong link credentials, accepting that this narrows network size and redundancy. Monitoring or rate-limiting inbound KILL traffic from peers can reduce exposure but is not a complete fix - the vendor's patch is the only complete remediation identified.

Affected VersionsENISA

solanum 0 <2ea1382e4262b212a91034258c466f0f6754cd61

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Solanum is an IRC daemon (ircd) that federates with other servers over the server-to-server IRC protocol; messages arriving on those links are dispatched to handlers such as ms_kill() in modules/core/m_kill.c, which processes KILL commands originated by a peer server. The flaw is CWE-120 (buffer copy without checking size of input): a kill reason string longer than KILLLEN is written into a static 512-byte buffer without a length check, corrupting adjacent memory. The upstream fix in PR #550 adds an explicit strlen(t) > KILLLEN check that truncates the reason to KILLLEN before further use. Because the vulnerable path is only reachable from an authenticated peer server, exploitation presupposes control of a rogue server or a compromised legitimate peer that already holds a configured, credentialed link block - a privileged trust relationship rather than an unauthenticated internet-facing surface.

Know when Solanum gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.5 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
vuln.today AI 7.2 HIGH

Requires control of a trusted linked peer server (PR:H) over the network with low complexity; overflow reliably crashes the ircd (A:H) and may yield code execution (C:H/I:H).

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Solanum before commit 2ea1382 contains a buffer overflow vulnerability in ms_kill() that allows malicious linked servers to corrupt memory by sending an overlong kill reason. Attackers controlling a rogue or compromised peer server can send a reason exceeding KILLLEN that overflows a static 512-byte buffer, crashing the ircd or potentially achieving remote code execution.

Executive ViewAI

Why It Matters

A high-severity memory corruption vulnerability in Solanum IRCd affects organizations operating IRC networks that link to peer servers. Exploitation requires an attacker to already control a trusted server-to-server link, enabling network disruption or potential code execution. This risk is material for critical communication channels but is limited to federated IRC deployments with build versions prior to commit 2ea1382.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

Prevalence
Low
niche IRC server daemon, limited and specialized deployment footprint
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS N/A
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy