Skip to main content
VulnerabilityPublished

CVE-2026-129804: FOE_read and FOE_write store the filename length as uint8_t, truncating it modulo 256

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-129804· Medium 4.2

Not known to be exploited · CVSS 4.2 Medium : upgrade to 3.2.1 when convenient.

Data as of 21 Nov 2026, 16:31 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (rt-labs)CVSS 3.14.2
Patch
Available – fixed in 3.2.1
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 20 Nov 2026.

What to do

Upgrade SOES to 3.2.1.

Affected software

ProductAffectedFixed in
RT-Labs ABSOESAffected
  • <3.2.1
Fixed in
  • 3.2.1

AI-suggested

If you cannot patch yet, restrict access to the affected functions and monitor for unusual file access patterns related to FOE_fopen calls with zero-length filename comparisons.

Description

The vulnerability CVE-2026-129804 involves FOE_read and FOE_write functions storing the filename length as a uint8_t, causing truncation modulo 256. This can result in a length of zero under specific conditions, leading FOE_fopen to incorrectly open the first registered file with a password of zero regardless of the requested filename.

References

Community reviews

Loading reviews…