CVE-2026-41146: boazsegev facil.io · Uncontrolled Resource Consumption
Affects boazsegev facil.ioSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 0.7.59 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.7.59
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Apr 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 29 Oct 2026.
What to do
Upgrade iodine to 0.7.59.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| boazsegevfacil.io | Affected
| Fixed in– |
| boazsegeviodine | Affected
| Fixed in
|
AI-suggested
A fix for this vulnerability is available in commit 5128747363055201d3ecf0e29bf0a961703c9fa0 of facil.io. Users should upgrade to a version that includes this commit to remediate the issue. Since no official vendor advisory or patch link is provided, users should monitor the facil.io project repository or vendor communications for an official release containing this fix. Until patched, consider restricting or validating JSON input to avoid nested values starting with 'i' or 'I' if feasible.
Description
CVE-2026-41146 is a high-severity vulnerability in facil.io, a C micro-framework for web applications. The issue involves uncontrolled resource consumption due to an infinite loop in the JSON parser function `fio_json_parse` when processing nested JSON values starting with the character 'i' or 'I'. This causes the process to consume 100% CPU on one core without returning a parse error. The vulnerability also affects the iodine project, which uses the same parser code. The issue is fixed in commit 5128747363055201d3ecf0e29bf0a961703c9fa0.