VulnerabilityPublished 12 Mar 2026

CVE-2026-4012: rxi fe · Out-of-bounds Read

Affects rxi feSource CVE Database V5

Compare

Public exploit available · CVSS 4.8 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score

4.8Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, 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

Affected software

Product	Affected	Fixed in
rxife	Affected =ed4cda96bd582cbb08520964ba627efb40f3dd91	Fixed in–

AI-suggested

To mitigate CVE-2026-4012, organizations should first restrict local access to trusted users only, minimizing the risk of exploitation by unauthorized personnel. Implement strict access controls and monitoring on systems running rxi fe to detect any suspicious local activity. Engage with the rxi fe community or maintainers to track patch releases or security advisories. Employ memory protection mechanisms such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) to reduce the impact of memory corruption issues. Conduct regular audits and vulnerability scans to identify the presence of vulnerable versions. If feasible, isolate systems running rxi fe in segmented network zones to limit lateral movement in case of compromise. Finally, prepare incident response plans that include this vulnerability to quickly address any exploitation attempts.

Description

A vulnerability was determined in rxi fe up to ed4cda96bd582cbb08520964ba627efb40f3dd91. The impacted element is the function read_ of the file src/fe.c. This manipulation with the input 1 causes out-of-bounds read. The attack requires local access. The exploit has been publicly disclosed and may be utilized. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The primary impact of CVE-2026-4012 is the potential exposure of sensitive memory contents due to out-of-bounds reading. Although it does not directly allow code execution or privilege escalation, the information leakage could facilitate further attacks, such as privilege escalation or data exfiltration, especially in environments where local access is already compromised. Systems running rxi fe locally, particularly on multi-user or shared environments, could be at risk of data leakage between users or processes. The medium severity reflects the limited scope and requirement for local access, but organizations with sensitive data or critical systems using rxi fe should consider this a significant risk. The lack of vendor response and patch availability increases the window of exposure. Additionally, the rolling release model may delay or complicate patch deployment, increasing operational risk. Overall, the threat is moderate but should not be ignored, especially in environments where local access controls are weak or where rxi fe is part of critical infrastructure.

Summary

CVE-2026-4012 identifies a security vulnerability in the rxi fe software, an open-source project that follows a rolling release update model. The vulnerability is an out-of-bounds read occurring in the read_ function within the src/fe.c source file. Specifically, when the function processes certain crafted input (noted as input '1'), it reads memory beyond the allocated buffer boundaries, potentially exposing sensitive information or causing undefined behavior. Exploitation requires local access and privileges, meaning an attacker must already have some level of access to the system to trigger the flaw. The vulnerability does not require user interaction and has low complexity for exploitation, but it does not allow privilege escalation or remote exploitation. The CVSS 4.0 vector indicates local attack vector (AV:L), low attack complexity (AC:L), no privileges required beyond local access (PR:L), no user interaction (UI:N), and limited impact on confidentiality (VC:L), with no impact on integrity or availability. The rxi fe project has not yet responded with a patch or mitigation, and due to the rolling release nature, specific affected versions are difficult to pinpoint. While no known exploits are currently active in the wild, the public disclosure of the exploit code increases the risk of future exploitation. This vulnerability primarily risks information disclosure through memory exposure, which could aid further attacks if combined with other vulnerabilities.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Mar 2026, 07:59 UTC

Technical details

References

Community reviews

Related threats