CVE-2026-48813
Flawfinder <2.0.20 allows ANSI/XML output injection via unsanitized filenames.
Is CVE-2026-48813 being exploited?
Not confirmed. CVE-2026-48813 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-48813?
CVE-2026-48813 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-48813?
Yes. A fix has been recorded for CVE-2026-48813. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-48813 affect?
CVE-2026-48813 affects Flawfinder < 2.0.20, Consumers of flawfinder output (CSV, SonarQube, CI pipelines). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-48813?
Upgrade Flawfinder to 2.0.20; sanitize/pre-scan filenames and restrict untrusted inputs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unsanitized filenames allow ANSI/terminal escape and XML injection: corrupt CSVs, inject attributes in SonarQube outputs, manipulate terminal output and taint reports/pipelines.
Patch when possible
- affected< 2.0.20
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.