flawfinder
Affected
- introduced
0, fixed2.0.20(ecosystem)
Fixed versions
2.0.20
Fix
- Fixed version
2.0.20pip install --upgrade flawfinder==2.0.20
Advisory
Also known as: CVE-2026-48813, GHSA-4c3c-r6p8-c863
Flawfinder output manipulation via untrusted filenames and source text
Impact
This vulnerability is an improper input neutralization issue leading to output manipulation, specifically, Terminal/ANSI Escape Sequence Injection and XML Injection:
It impacts those who use flawfinder to evaluate intentionally malicious filenames or file contents.
The initial filename injection problem was reported by Dan Lenz https://www.linkedin.com/in/dan-lenz/
The other vulnerabilities were found by flawfinder project leader David A. Wheeler, GitHub david-a-wheeler, https://dwheeler.com/
Patches
This issue has been fully patched in Version 2.0.20 (released 2026-05-16). All users should upgrade to version 2.0.20 or later immediately. If you use Python's package manager, you can upgrade using pip install --upgrade flawfinder. If you are consuming flawfinder via GitHub Actions, ensure your workflow points to david-a-wheeler/[email protected] or later.
Workarounds
There is no configuration-based workaround within older versions of flawfinder. If an immediate upgrade is not possible, users can mitigate the risk by:
Resources
See the flawfinder GitHub Repository: https://github.com/david-a-wheeler/flawfinder
Not rated by the source.
0, fixed 2.0.20 (ecosystem)2.0.20
2.0.20pip install --upgrade flawfinder==2.0.20Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0