VulnerabilityPublished 24 Mar 2026

CVE-2026-4733: ixray-1.6-stcop · Information Exposure

Affects ixray-1.6-stcopSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.3 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% 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:L

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

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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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

Since no patches are currently available, organizations should implement compensating controls to mitigate risk. These include restricting network access to the ixray-1.6-stcop service using firewalls or network segmentation to limit exposure to trusted hosts only. Employ intrusion detection and prevention systems (IDS/IPS) to monitor for unusual access patterns or data exfiltration attempts targeting the affected software. Conduct thorough audits of system configurations and logs to detect any unauthorized access or data leakage. Engage with the vendor (ixray-team) to obtain updates on patch releases and apply them promptly once available. Additionally, consider deploying application-layer gateways or reverse proxies that can enforce stricter access controls and sanitize responses to prevent sensitive data exposure. Regularly update and train security teams on emerging threats related to this product. Finally, maintain an incident response plan tailored to data exposure incidents to minimize impact if exploitation occurs.

Description

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in ixray-team ixray-1.6-stcop.This issue affects ixray-1.6-stcop: before 1.3.

Impact

The primary impact of CVE-2026-4733 is unauthorized exposure of sensitive information, which can compromise organizational confidentiality indirectly by revealing internal data that may aid attackers in crafting more effective attacks. Although the CVSS vector indicates no direct confidentiality or integrity loss, the availability impact suggests potential service disruption or degradation. Organizations relying on ixray-1.6-stcop versions before 1.3 may face risks of data leakage, which could include configuration details, user information, or system metadata. This exposure can lead to increased attack surface and potential exploitation by malicious actors. The lack of authentication or user interaction requirements makes the vulnerability easier to exploit remotely, increasing the risk profile. However, the absence of known exploits in the wild and the medium severity rating suggest that the threat is moderate at present but could escalate if weaponized. The impact is more significant for organizations in sensitive sectors such as government, defense, or critical infrastructure that use this product.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Mar 2026, 03:48 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats