CVE-2026-24831VulnerabilityPublished 27 Jan 2026

CVE-2026-24831: ixray-1.6-stcop · Infinite Loop

Affects ixray-1.6-stcopSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.3 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade ixray-1.6-stcop and ixray-team/ixray-1.6-stcop to 1.3.

Affected software

Product	Affected	Fixed in
ixray-teamixray-1.6-stcop	Affected <1.3	Fixed in 1.3
GitHubixray-team/ixray-1.6-stcop`pkg:github/ixray-team/ixray-1.6-stcop`Other threats	Affected <1.3	Fixed in 1.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor system and application logs for unusual CPU or memory usage patterns indicative of infinite loops. 2. Implement network-level protections such as firewalls and intrusion prevention systems (IPS) to restrict access to the ixray-1.6-stcop service from untrusted sources. 3. Employ rate limiting and anomaly detection to identify and block suspicious traffic that may trigger the vulnerability. 4. Isolate critical systems running ixray-1.6-stcop in segmented network zones to limit potential impact. 5. 6. Consider temporary workarounds such as disabling or restricting vulnerable features if feasible. 7. Conduct regular backups and ensure disaster recovery plans are tested to mitigate operational disruptions. 8. Educate security teams about this vulnerability to improve detection and response capabilities.

Description

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in ixray-team ixray-1.6-stcop.This issue affects ixray-1.6-stcop: before 1.3.

Impact

For European organizations, the impact of CVE-2026-24831 primarily involves availability disruptions. Organizations relying on ixray-1.6-stcop for critical operations may experience service outages or degraded performance due to the infinite loop consuming system resources. This can affect business continuity, especially in sectors where uptime is crucial such as finance, healthcare, telecommunications, and public services. The lack of authentication or user interaction requirements means attackers can remotely trigger the vulnerability, increasing the risk of widespread denial of service attacks. Although no data breach or integrity compromise is expected, the operational impact can lead to financial losses, reputational damage, and potential regulatory scrutiny under frameworks like GDPR if service disruptions affect personal data processing. Additionally, the absence of patches means organizations must rely on interim mitigations, increasing exposure duration. The threat is more severe for environments with high network exposure or limited monitoring capabilities.

References

github.com/ixray-team/ixray-1.6-stcop/pull/248 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Jan 2026, 16:05 UTC

WeaknessesCWE-835

Technical details

References

Community reviews

Related threats