CVE-2026-46643: Snappy: Binary path is never shell-escaped due to an inverted is_executable check

unknownCVE-2026-46643

CSIRTS triage

Other

What: The binary path is not shell-escaped due to an inverted check.
Who is affected: Deployments using the Snappy library.
Urgency: Remediation is necessary due to potential security implications.
Action: Apply the relevant patches as they become available.

AI-assisted analysis generated from the source advisory — verify against the original.

Details

Source: Microsoft Security Response Center (INTL · vendor-psirt · site)
Severity: unknown
Published: 2026-06-09
Exploitation: Not in CISA KEV at last sync

Original advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-46643

Exploitation outlook

EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.

Low exploitation riskCVE-2026-466430.15% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 5% of all EPSS-scored CVEs.

Referenced CVEs

CVE	CSIRTS overview	External
CVE-2026-46643	coverage & exploitation status	NVD · CVE.org

Recent advisories for Snappy

A cluster of recent advisories against the same product widens the attack surface — attackers routinely chain freshly published CVEs on one product, so review these together.

criticalCVE-2023-28115: Snappy vulnerable to PHAR deserialization, allowing remote code executionmsrc · 2026-08-06
unknownCVE-2026-46683: Snappy: SSRF and local file read via the xsl-style-sheet optionmsrc · 2026-06-09