A flaw was found in ansible-core. The _extract_collection_from_git() function in ansible-core's concrete_artifact_manager.py constructs git clone commands without a '--' (end-of-options) separator before user-supplied URLs when installing collections from git sources. An attacker who provides a crafted collection source URI containing git argument injection payloads can achieve arbitrary command execution when a user runs 'ansible-galaxy collection install' with the malicious source. This is an incomplete fix for CVE-2026-11332, which hardened the role install path but missed the equivalent collection install code path.
CVE-2026-16493
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-21. a secondary CVSS source baseline 7.8; sources differ by 0.0.
- 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.8
- EG Score
- 7.8(high)
- 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 computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 23.8%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 22, 2026
Advisory Details (2)
Auto-updated Jul 21, 20262503724 – (CVE-2026-16493) CVE-2026-16493 ansible-core: argument injection in ansible-galaxy collection install via git clone (incomplete fix for CVE-2026-11332)
https://bugzilla.redhat.com/show_bug.cgi?id=2503724Vendor Advisories for CVE-2026-16493(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× 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-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:06 UTCEG score recompute
- 2026-07-22 23:04 UTCEG score recompute
- 2026-07-22 23:04 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 20:08 UTCEG score recompute
- 2026-07-21 20:08 UTCGHSA enrichment
- 2026-07-21 17:40 UTCEG score recompute
- 2026-07-21 17:38 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-88
- CVE-2018-3856EG 9.9CRITICAL
- CVE-2020-28026EG 9.8EPSS 95%CRITICAL
- CVE-2020-21224EG 9.8EPSS 98%CRITICAL
- CVE-2020-25494EG 9.8EPSS 98%CRITICAL
- CVE-2020-5648EG 9.8CRITICAL
- CVE-2020-15692EG 9.8EPSS 90%CRITICAL
- CVE-2020-5599EG 9.8CRITICAL
- CVE-2020-12641EG 9.8 KEVEPSS 100%CRITICAL
- CVE-2019-12148EG 9.8CRITICAL
- CVE-2019-12147EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-16493?
When was CVE-2026-16493 disclosed?
Is CVE-2026-16493 actively exploited?
What is the CVSS score of CVE-2026-16493?
How do I remediate CVE-2026-16493?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16493
Is Your Infrastructure Affected by CVE-2026-16493?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.