Bug 2514994 - CVE-2026-48813 flawfinder: output manipulation via untrusted filenames and source text [fedora-all]
Summary: CVE-2026-48813 flawfinder: output manipulation via untrusted filenames and so...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: flawfinder
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Athos Ribeiro
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["97962510-1251-4fcd-8148-d...
Depends On:
Blocks: CVE-2026-48813
TreeView+ depends on / blocked
 
Reported: 2026-08-12 21:03 UTC by Guilherme de Almeida Suckevicz
Modified: 2026-08-12 21:03 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2026-08-12 21:03:17 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.


Note You need to log in before you can comment on or make changes to this bug.