CVE-2024-23722: fluent-bit · NULL Pointer Dereference
Affects fluent-bitSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfluent/fluent-bitpkg:github/fluent/fluent-bitOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediately monitor Fluent Bit instances for crashes and failures to restart, implementing alerting to detect this condition quickly.
- Restrict network access to Fluent Bit HTTP endpoints to trusted sources only, using firewall rules or network segmentation to reduce exposure.
- If possible, disable or limit processing of HTTP payloads with content type x-www-form-urlencoded until a patch is available.
- Implement process supervision or orchestration tools (e.g., systemd, Kubernetes liveness probes) to automatically restart Fluent Bit upon crashes to minimize downtime.
- Review Fluent Bit configurations to ensure minimal exposure of HTTP input plugins or endpoints.
- Stay updated with Fluent Bit vendor announcements and apply patches promptly once released.
- Consider deploying additional logging redundancy or alternative log forwarders temporarily to maintain log continuity.
- Conduct internal testing with malformed HTTP payloads in a controlled environment to understand the impact and validate mitigations.
Description
In Fluent Bit 2.1.8 through 2.2.1, a NULL pointer dereference can be caused via an invalid HTTP payload with the content type of x-www-form-urlencoded. It crashes and does not restart. This could result in logs not being delivered properly.