BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-16493High confidence

Ansible-core: argument injection in ansible-galaxy collection install via git clone (incomplete fix for cve-2026-11332)

Red Hat · Red Hat Satellite 6.17 for RHEL 9

Official source article: Red Hat RHSA-2026:63385 ↗. Check the applicable product and release in the original source.

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.17% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Red Hat Red Hat Satellite 6.17 for RHEL 9 and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

10 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourceansibleVendor fix publishedDebian records a fixed source-package version for this release.5.4.0-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian trixietrixie · sourceansible-coreAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourceansibleVendor fix publishedDebian records a fixed source-package version for this release.5.4.0-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourceansible-coreAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourceansibleVendor fix publishedDebian records a fixed source-package version for this release.5.4.0-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourceansible-coreAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourceansibleVendor fix publishedDebian records a fixed source-package version for this release.5.4.0-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourceansible-coreAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveansibleUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveansible-coreUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-16493 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityansible-core: argument injection in ansible-galaxy collection install via git clone (incomplete fix for CVE-2026-11332)
10 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • ansible-core.src as a component of Red Hat Ansible Automation Platform 2
  • ansible-core as a component of Red Hat Enterprise Linux 10
  • ansible-core.src as a component of Red Hat Enterprise Linux 10
  • ansible-test as a component of Red Hat Enterprise Linux 10
  • ansible-core as a component of Red Hat Enterprise Linux 8
  • ansible-core.src as a component of Red Hat Enterprise Linux 8
  • ansible-test as a component of Red Hat Enterprise Linux 8
  • ansible-core as a component of Red Hat Enterprise Linux 9
  • ansible-core.src as a component of Red Hat Enterprise Linux 9
  • ansible-test as a component of Red Hat Enterprise Linux 9
Summary
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.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_satellite/6.17/html/updating_red_hat_satellite/index
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-46336

No EUVD known-exploited evidence

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.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-88 ↗

CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection'). The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
UnauthenticatedCWE-88
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-46336Official EUVD mapping

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.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2462Ansible: Schwachstelle ermöglicht Codeausführung

Ein lokaler Angreifer kann eine Schwachstelle in Ansible ausnutzen, um beliebigen Programmcode auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260722Security Bulletin 22 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jul 2026, published on 22 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 21 Jul 2026 · Last source change 4 Sept 2026, 02:01 UTC · CWE-88 · Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-46336
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added remediation: access.redhat.com/RHSA-2026:63385.
    Before
    no authoritative guidance recorded
    After
    remediation: access.redhat.com/RHSA-2026:63385
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    See the vendor and CVE records for the affected range. · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    See the vendor and CVE records for the affected range. · Fixed: Red Hat Satellite 6.17 for RHEL 9: 1:2.16.19-1.el9sat < *; Red Hat Satellite 6.18 for RHEL 9: 1:2.16.19-1.el9sat < *, 0:1.3.1-5.el9pc < *, 0:3.73.30-3.el9pc < *; Red Hat Satellite 6.19 for RHEL 9: 1:2.16.19-1.el9sat < *
    CNA ↗
  3. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    CNA ↗
  4. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:63385; removed vendor advisory: access.redhat.com/RHSA-2026:63386.
    Before
    remediation: access.redhat.com/RHSA-2026:63385 · vendor advisory: access.redhat.com/RHSA-2026:63385 · vendor advisory: access.redhat.com/RHSA-2026:63386
    After
    remediation: access.redhat.com/RHSA-2026:63385
    CNA ↗
  5. Vendor guidanceAuthoritative vendor guidance changed: added remediation: access.redhat.com/RHSA-2026:63385; added vendor advisory: access.redhat.com/RHSA-2026:63385; removed remediation: access.redhat.com/RHSA-2026:63387; 1 further additions.
    Before
    remediation: access.redhat.com/RHSA-2026:63387
    After
    remediation: access.redhat.com/RHSA-2026:63385 · vendor advisory: access.redhat.com/RHSA-2026:63385 · vendor advisory: access.redhat.com/RHSA-2026:63386
    access.redhat.com ↗
  6. Affected versionsThe structured affected or fixed version information changed.
    Before
    See the vendor and CVE records for the affected range. · Fixed: 1:2.16.19-1.el9sat < *
    After
    See the vendor and CVE records for the affected range. · Fixed: 1:2.16.19-1.el9sat < *; 0:1.3.1-5.el9pc < *; 0:3.73.30-3.el9pc < *
    CNA ↗
  7. Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHSA-2026:63387.
    Before
    remediation: access.redhat.com/RHSA-2026:63387 · vendor advisory: access.redhat.com/RHSA-2026:63387
    After
    remediation: access.redhat.com/RHSA-2026:63387
    CNA ↗
  8. Vendor guidanceAuthoritative vendor guidance changed: added remediation: access.redhat.com/RHSA-2026:63387; added vendor advisory: access.redhat.com/RHSA-2026:63387.
    Before
    no authoritative guidance recorded
    After
    remediation: access.redhat.com/RHSA-2026:63387 · vendor advisory: access.redhat.com/RHSA-2026:63387
    access.redhat.com ↗
  9. Affected versionsThe structured affected or fixed version information changed.
    Before
    See the vendor and CVE records for the affected range. · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    See the vendor and CVE records for the affected range. · Fixed: 1:2.16.19-1.el9sat < *
    CNA ↗
  10. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    access.redhat.com ↗
  11. Vendor guidanceAuthoritative vendor guidance changed: removed remediation: access.redhat.com/RHSA-2026:63385.
    Before
    remediation: access.redhat.com/RHSA-2026:63385
    After
    no authoritative guidance recorded
    CNA ↗
  12. Affected versionsThe structured affected or fixed version information changed.
    Before
    See the vendor and CVE records for the affected range. · Fixed: 1:2.16.19-1.el9sat < *; 0:1.3.1-5.el9pc < *; 0:3.73.30-3.el9pc < *
    After
    See the vendor and CVE records for the affected range. · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  13. Remediation statusRemediation status changed from Patch available to Awaiting fix.
    Before
    Patch available
    After
    Awaiting fix
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-46336↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference · Red Hat RHSA-2026:63385↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-16493 · cve.blacktree.nl