CVE-2026-129807: The FoE file table allows entries to omit a write handler by setting write_function to NULL, making
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.2.1 when convenient.
Data as of 21 Nov 2026, 16:30 UTC
Thin evidence
One scorer or none| CNA (rt-labs) | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 3.2.1
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 20 Nov 2026.
What to do
Upgrade SOES to 3.2.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| RT-Labs ABSOES | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, avoid sending write requests to files known to be read-only in the FoE file table to prevent triggering the NULL pointer dereference.
Description
CVE-2026-129807 describes a vulnerability in the FoE file table where entries can omit a write handler by setting write_function to NULL, making the file read-only. The FOE_fopen function did not verify the presence of a write handler before processing write requests, leading to a NULL pointer dereference when a write request (WRQ) was sent for a read-only file.