Answer in brief
CVE-2026-129804 records a Medium severity (CVSS 4.2) vulnerability in FoE Filename Matching Bypass via Length Truncation. The current sources do not mark it as known exploited. The current feed maps RT-Labs AB/SOES (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps RT-Labs AB/SOES (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| RT-Labs AB/SOESgeneric | >=0 <3.2.1 | 3.2.1 |
Published upstream
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 21, 2026
FOE_read and FOE_write store the filename length as uint8_t, truncating it modulo 256. When (mbxheader.length - ESC_FOEHSIZE) is a multiple of 256, the length becomes 0. Additionally, a request whose mailbox length equals ESC_FOEHSIZE exactly also produces a length of 0 without any truncation. In both cases FOE_fopen calls strncmp with a length of 0, which always returns equal, so the first registered file whose password is 0 is opened regardless of the filename the master sent.
Quoted source text, attributed separately from HOL analysis.