In openshift-metal3/fakefish there is a repeated pattern in some of the scripts where shell variables are injected without quoting them either into command lines or into manifests. This mostly applies to the Image URL and BMC credentials (which are not verified by FakeFish).
CVE-2026-71567
This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.7
- EG Score
- 7.7(medium)
- EG Risk
- 35(Track)EG Risk 35/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 computedSeverity77% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 9%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 17, 2026
Advisory Details (1)
Auto-updated Aug 17, 2026User-controlled variables inserted unescaped into shell scripts and Kubernetes manifests · Advisory · openshift-metal3/fakefish · GitHub
https://github.com/openshift-metal3/fakefish/security/advisories/GHSA-xfhv-fp7q-v2ccWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 25× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 05:38 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 22:20 UTCEG score recompute
- 2026-08-26 21:50 UTCEG score recompute
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 21:06 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 20:38 UTCEG score recompute
- 2026-08-23 07:52 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 07:25 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 06:58 UTCEG score recompute
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 18:17 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 16:58 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 16:22 UTCEG score recompute
- 2026-08-17 16:10 UTCEG score recompute
- 2026-08-17 15:20 UTCEG score recompute
- 2026-08-17 14:44 UTCEG score recompute
- 2026-08-17 14:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
- CVE-2009-20011EG 10.0CRITICAL
- CVE-2011-10017EG 10.0CRITICAL
- CVE-2012-1166EG 10.0EPSS p91HIGH
- CVE-2012-2976EG 10.0EPSS p92HIGH
- CVE-2012-2953EG 10.0EPSS p99HIGH
- CVE-2011-4502EG 10.0EPSS p92HIGH
- CVE-2011-2148EG 10.0EPSS p92HIGH
- CVE-2011-0382EG 10.0EPSS p90HIGH
- CVE-2011-0381EG 10.0EPSS p92HIGH
- CVE-2011-0372EG 10.0HIGH
Frequently asked(5)
What is CVE-2026-71567?
When was CVE-2026-71567 disclosed?
Is CVE-2026-71567 actively exploited?
What is the CVSS score of CVE-2026-71567?
How do I remediate CVE-2026-71567?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-71567
Is Your Infrastructure Affected by CVE-2026-71567?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.