AUGUST 15, 2026
Live Feed
Back to database
Case File

CVE-2026-48813

HIGH · CVSS 8.7 EPSS 0.33% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-08-11 · Last synced 2026-08-15

CyberRota Analysis

AI-Generated

Flawfinder versions prior to 2.0.20 are vulnerable to improper input neutralization, allowing attackers to exploit terminal output through Terminal/ANSI Escape Sequence Injection and XML Injection. This can lead to corrupted CSV formats and arbitrary XML attribute injection in SonarQube outputs, posing significant risks for users evaluating potentially malicious filenames or contents. Organizations utilizing Flawfinder for static analysis should prioritize upgrading to version 2.0.20 or implement mitigation strategies to safeguard against these vulnerabilities.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Detected Signals
exploit
GitHub PoC Links

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-48813
Severity
HIGH
CVSS
8.7
EPSS
0.33%

Original NVD Description

Flawfinder is a a static analysis tool for finding vulnerabilities in C/C++ source code. Versions prior to 2.0.20 have an improper input neutralization issue leading to output manipulation, specifically, Terminal/ANSI Escape Sequence Injection and XML Injection. A malicious file whose name contains ANSI escape sequences can end up being included in flawfinder's standard terminal output, with many effects. Untrusted fields (such as filenames, categories, or code context text) were not properly sanitized when generating structured reports. An attacker could exploit this to corrupt CSV formats or inject arbitrary XML attributes into SonarQube outputs via output_sonar(). It impacts those who use flawfinder to evaluate intentionally malicious filenames or file contents. This issue has been fully patched in Version 2.0.20 (released 2026-05-16). There is no configuration-based workaround within older versions of flawfinder. If an immediate upgrade is not possible, users can mitigate the risk by pre-scanning filenames, inspecting raw output, and/or restricting untrusted inputs.