CVE-2026-48813

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

June 26, 2026

Last Modified

August 12, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
Patch available. Sources: github.
github Patch Available

Flawfinder output manipulation via untrusted filenames and source text · Advisory · david-a-wheeler/flawfinder · GitHub

Affected: Version 2.0.20 (released 2026-05-16). All users should upgrade to version 2.0.20

https://github.com/david-a-wheeler/flawfinder/security/advisories/GHSA-4c3c-r6p8-c863

Vendor Advisories for CVE-2026-48813(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
flawfinder2.0.10 ... 2.0.9 (15 versions)2.0.20—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 19:20 UTCEG score recompute
  2. 2026-08-30 19:17 UTCEPSS rescore
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 23:00 UTCEG score recompute
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-25 01:14 UTCEG score recompute
  10. 2026-08-24 12:52 UTCEG score recompute
  11. 2026-08-23 10:27 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 09:24 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 07:29 UTCEG score recompute
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 06:44 UTCEG score recompute
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-18 23:41 UTCEG score recompute
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-16 18:17 UTCEG score recompute
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 05:10 UTCEG score recompute
  25. 2026-08-16 02:14 UTCEPSS rescore
Show 14 more
  1. 2026-08-15 04:25 UTCEG score recompute
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 03:33 UTCEG score recompute
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-12 14:27 UTCEG score recompute
  6. 2026-08-12 13:51 UTCEPSS rescore
  7. 2026-08-12 13:26 UTCEG score recompute
  8. 2026-08-11 20:21 UTCEG score recompute
  9. 2026-08-11 19:30 UTCEG score recompute▲ 8.70
  10. 2026-08-11 19:30 UTCMITRE cvelistV5CVSS v3 → 8.7 · CVSS v4 → 8.7 · severity → HIGH
  11. 2026-08-01 10:18 UTCEG score recompute
  12. 2026-07-26 14:31 UTCEG score recompute
  13. 2026-07-23 03:18 UTCEG score recompute
  14. 2026-06-26 21:40 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48813?
CVE-2026-48813 is a high vulnerability published on June 26, 2026. 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…
When was CVE-2026-48813 disclosed?
CVE-2026-48813 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48813 actively exploited?
CVE-2026-48813 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.9% of all scored CVEs.
What is the CVSS score of CVE-2026-48813?
CVE-2026-48813 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-48813?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48813, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48813

Explore →

Is Your Infrastructure Affected by CVE-2026-48813?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs