VulnerabilityPublished 27 Jan 2026

CVE-2026-24874: themrdemonized xray-monolith · Type Confusion

Affects themrdemonized xray-monolithSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical : upgrade to 2025.12.30 as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

9.1Critical

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 2025.12.30

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

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

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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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 xray-monolith and themrdemonized/xray-monolith to 2025.12.30.

Affected software

Product	Affected	Fixed in
themrdemonizedxray-monolith	Affected <2025.12.30	Fixed in 2025.12.30
GitHubthemrdemonized/xray-monolith`pkg:github/themrdemonized/xray-monolith`Other threats	Affected <2025.12.30	Fixed in 2025.12.30

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

AI-suggested

Immediate action should include inventorying all instances of themrdemonized xray-monolith to identify affected versions prior to 2025.12.30.
Monitor vendor communications closely for official patches or updates addressing CVE-2026-24874 and apply them promptly once available.
Implement network-level protections such as firewall rules or segmentation to restrict access to xray-monolith services from untrusted networks.
Employ runtime application self-protection (RASP) or memory safety tools that can detect and prevent type confusion or memory corruption exploits.
Conduct thorough code audits and static analysis if custom or extended versions of xray-monolith are used, focusing on type handling and casting operations.
Enhance logging and monitoring to detect anomalous access patterns or unexpected resource usage indicative of exploitation attempts.
Educate development and security teams about type confusion vulnerabilities and secure coding practices to prevent similar issues in future software versions.
Consider deploying application-layer intrusion detection systems (IDS) tailored to detect exploitation attempts targeting this vulnerability.

Description

Access of Resource Using Incompatible Type ('Type Confusion') vulnerability in themrdemonized xray-monolith.This issue affects xray-monolith: before 2025.12.30.

Impact

For European organizations, the impact of CVE-2026-24874 is significant due to the critical nature of the vulnerability. Organizations using themrdemonized xray-monolith in sectors such as government, finance, healthcare, or critical infrastructure could face severe confidentiality breaches and data integrity compromises. The ability to exploit this vulnerability remotely without authentication increases the attack surface and risk of widespread exploitation. Data theft, unauthorized data manipulation, or further system compromise could result, leading to regulatory penalties under GDPR for data breaches and loss of trust. The absence of known exploits currently provides a window for proactive mitigation, but the critical CVSS score demands immediate risk assessment and remediation planning. Disruption of sensitive operations or exposure of confidential information could have cascading effects on business continuity and national security interests within Europe.

References

github.com/themrdemonized/xray-monolith/pull/399 (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:20 UTC

WeaknessesCWE-843

Technical details

References

Community reviews

Related threats