rxi fe fe.c read_ out-of-bounds
Key facts
- Attack vector
- Local
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-125 and the CVSS impact.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-4012
- 2026-10-03 Alias added: GHSA-jw4f-7h4g-j7fj
References
More rxi vulnerabilities
- TI-2026-31728 microtar 0.1.0 Stack-Based Buffer Overflow via raw_to_header() CVSS 4.0HIGH 8.7
- TI-2026-49935 microtar Stack Buffer Overflow in mtar_write_file_header() and mtar_write_dir_header() CVSS 3.1CRITICAL 9.8
- TI-2026-40236 Stack Buffer Overflow in rxi/microtar raw_to_header() via non-null-terminated TAR name field CVSS 4.0HIGH 8.7
- TI-2026-39293 Integer Overflow in rxi/microtar mtar_next() Causes Infinite Loop DoS CVSS 4.0HIGH 8.7
Sources
- CVE-2026-4012 · CVE Program
- CVE-2026-4012 · NVD
- FIRST EPSS
- GHSA-jw4f-7h4g-j7fj · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences