Skip to main content
VulnerabilityPublished

CVE-2026-24832: ixray-1.6-stcop · Out-of-bounds Write

Affects ixray-1.6-stcopSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.3 as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% 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:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade ixray-1.6-stcop to 1.3.

Affected software

ProductAffectedFixed in
ixray-teamixray-1.6-stcopAffected
  • <1.3
Fixed in
  • 1.3

AI-suggested

  1. Immediately identify and inventory all instances of ixray-1.6-stcop within the organization to assess exposure.
  2. Implement network segmentation and restrict inbound network access to systems running the vulnerable software to limit attack surface.
  3. Deploy intrusion detection and prevention systems (IDS/IPS) with updated signatures to detect anomalous memory corruption attempts.
  4. Monitor logs and network traffic for unusual behavior indicative of exploitation attempts, such as unexpected process executions or memory access violations.
  5. 6. If patches are not yet available, consider temporary mitigations such as disabling or isolating vulnerable components or applying application-level firewalls. 7. Conduct regular vulnerability scanning and penetration testing focused on this vulnerability to validate defenses. 8. Educate security teams about the specific characteristics of out-of-bounds write exploits to improve incident response readiness. 9. Review and enhance backup and recovery procedures to mitigate potential ransomware or destructive attacks leveraging this vulnerability. 10. Coordinate with European cybersecurity agencies for threat intelligence sharing and guidance.

Description

Out-of-bounds Write vulnerability in ixray-team ixray-1.6-stcop.This issue affects ixray-1.6-stcop: before 1.3.

References

Community reviews

Loading reviews…