BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2024-58266High confidence

The shlex crate before 1.2.1 for Rust allows unquoted and unescaped instances of the { and \xa0 characters, which may facilitate command injection

comex · shlex

Official source article: GitHub GHSA-R7QV-8R2H-PG27 ↗. Check the applicable product and release in the original source.

3.2LowCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 41 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 severityLowOperational priority:Low, unchanged from published severity.unchanged

Evidence used

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

Compensating controls

  • Apply the linked authoritative mitigation while planning the permanent fix.
  • 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 comex shlex and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  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: No default targetRemediation target: Normal maintenance

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 41 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.

5 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 1 affected package state 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 · sourcerust-shlexVendor fix publishedDebian records a fixed source-package version for this release.1.3.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcerust-shlexAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcerust-shlexVendor fix publishedDebian records a fixed source-package version for this release.1.3.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcerust-shlexVendor fix publishedDebian records a fixed source-package version for this release.1.3.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiverust-shlexUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges1 source-attributed range

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
rustshlex< 1.3.01.3.0GitHub advisory ↗upstream repository advisory · 28 Jul 2025
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-2024-58266 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityshlex: Shlex Command Injection Vulnerability
40 known affected

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

  • openshift-logging/cluster-logging-operator-bundle as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/cluster-logging-rhel9-operator as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/eventrouter-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/log-file-metric-exporter-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/vector-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-service-mesh-dev-preview-beta/istio-ztunnel-rhel9 as a component of OpenShift Service Mesh 3
  • openshift-service-mesh/istio-cni-rhel9 as a component of OpenShift Service Mesh 3
  • openshift-service-mesh/istio-must-gather-rhel9 as a component of OpenShift Service Mesh 3
  • openshift-service-mesh/istio-pilot-rhel9 as a component of OpenShift Service Mesh 3
  • openshift-service-mesh/istio-proxyv2-rhel9 as a component of OpenShift Service Mesh 3
  • openshift-service-mesh/istio-rhel9-operator as a component of OpenShift Service Mesh 3
  • openshift-service-mesh/istio-sail-operator-bundle as a component of OpenShift Service Mesh 3
Summary
A flaw was found in shlex. The shlex crate improperly handles unquoted and unescaped curly brace and non-breaking space characters, allowing a local attacker to inject arbitrary commands. This injection occurs when processing input that contains these characters without proper quoting or escaping. Successful exploitation results in the execution of attacker-controlled commands. This can lead to arbitrary code execution.
Remediation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
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-2024-54826

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 41 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

The shlex crate before 1.2.1 for Rust allows unquoted and unescaped instances of the { and \xa0 characters, which may facilitate command injection.

What

The shlex crate before 1.2.1 for Rust allows unquoted and unescaped instances of the { and \xa0 characters, which may facilitate command injection.

Why

The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.

How

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

What

The shlex crate before 1.2.1 for Rust allows unquoted and unescaped instances of the { and \xa0 characters, which may facilitate command injection.

Why

The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.

How

An attacker operating through local access may attempt exploitation without authentication or 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 Encoding or Escaping of Output → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-116 ↗

CWE-116: Improper Encoding or Escaping of Output. The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.

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:H/PR:N/UI:N/S:C/C:N/I:L/A:N

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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
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-116
A

Official authority intelligence

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

Cyber Security Agency of Singapore · English · CSA-SB-20250730Security Bulletin 30 Jul 2025 [827KB]

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 30 Jul 2025 [827KB], published on 30 July 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

d?id=CVE-2024-58080 Référence CVE CVE-2024-58081 https://www.cve.org/CVERecord?id=CVE-2024-58081 Référence CVE CVE-2024-58082 https://www.cve.org/CVERecord?id=CVE-2024-58082 Référence CVE CVE-2024-58083 https://www.cve.org/CVERecord?id=CVE-2024-58083 Référence CVE CVE-2024-58085 https://www.cve.org/CVERecord?id=CVE-2024-58085 Référence CVE CVE-2024-58086 https://www.cve.org/CVERecord?id=CVE-2024-58086 Référence CVE CVE-2024-58088 https://www.cve.org/CVERecord?id=CVE-2024-58088 Référence CVE CVE-2024-58090 https://www.cve.org/CVERecord?id=CVE-2024-58090 Référence CVE CVE-2024-58093 https://www.cve.org/CVERecord?id=CVE-2024-58093 Référence CVE CVE-2024-58266 https://www.cve.org/CVERecord?id=CVE-2024-58266 Référence CVE CVE-2024-6119 https://www.cve.org/CVERecord?id=CVE-2024-6119 Référence CVE CVE-2024-6174 https://www.cve.org/CVERecord?id=CVE-2024-6174 Référence CVE CVE-2024-6232 https://www.cve.org/CVERecord?id=CVE-2024-6232 Référence CVE CVE-2024-6345 https://www.cve.org/CVERecord?id=CVE-2024-6345 Référence CVE CVE-2024-6923 https://www.cve.org/CVERecord?id=CVE-2024-6923 Référence CVE CVE-2024-7254 https://www.cve.org/CVERecord?id=CVE-2024-7254 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-7592 https://www.cve.org/CVERecord?id=CVE-2024-7592 R

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0967Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2024-43485 Référence CVE CVE-2024-4467 https://www.cve.org/CVERecord?id=CVE-2024-4467 Référence CVE CVE-2024-45336 https://www.cve.org/CVERecord?id=CVE-2024-45336 Référence CVE CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 Référence CVE CVE-2024-45341 https://www.cve.org/CVERecord?id=CVE-2024-45341 Référence CVE CVE-2024-47535 https://www.cve.org/CVERecord?id=CVE-2024-47535 Référence CVE CVE-2024-47554 https://www.cve.org/CVERecord?id=CVE-2024-47554 Référence CVE CVE-2024-50602 https://www.cve.org/CVERecord?id=CVE-2024-50602 Référence CVE CVE-2024-5642 https://www.cve.org/CVERecord?id=CVE-2024-5642 Référence CVE CVE-2024-58266 https://www.cve.org/CVERecord?id=CVE-2024-58266 Référence CVE CVE-2024-6232 https://www.cve.org/CVERecord?id=CVE-2024-6232 Référence CVE CVE-2024-6505 https://www.cve.org/CVERecord?id=CVE-2024-6505 Référence CVE CVE-2024-6923 https://www.cve.org/CVERecord?id=CVE-2024-6923 Référence CVE CVE-2024-7409 https://www.cve.org/CVERecord?id=CVE-2024-7409 Référence CVE CVE-2024-7592 https://www.cve.org/CVERecord?id=CVE-2024-7592 Référence CVE CVE-2024-8088 https://www.cve.org/CVERecord?id=CVE-2024-8088 Référence CVE CVE-2024-8244 https://www.cve.org/CVERecord?id=CVE-2024-8244 Référence CVE CVE-2024-9287 https://www.cve.org/CVERecord?id=CVE-2024-9287 R

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-011281comex の Rust 用 shlex におけるエンコードおよびエスケープに関する脆弱性

comex の Rust 用 shlex には、エンコードおよびエスケープに関する脆弱性が存在します。

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
No fixed version is explicitly recorded in the structured CVE data.
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
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
04

Evidence and provenance

Published 27 Jul 2025 · Last source change 28 Jul 2025, 15:03 UTC · CWE-116 · Improper Encoding or Escaping of Output

CVE recordCVE.org · 5.1
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-2024-54826
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

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

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2024-54826↗Vendor CSAF · Red Hat Product Security↗Vendor advisory · GitHub GHSA-R7QV-8R2H-PG27↗CVE authority or vendor reference↗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-2024-58266 · cve.blacktree.nl