critical

CVE-2024-51736

CVE-2024-51736: Command execution hijack on Windows with Process class

Published 6 Nov 2024Modified 17 Jun 2026CWE 77

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

NVD9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

GHSA8.6CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Trivy's own label is CRITICAL. Rated critical by NVD. Rated lower by GHSA (high).

Description

Symphony process is a module for the Symphony PHP framework which executes commands in sub-processes. On Windows, when an executable file named `cmd.exe` is located in the current working directory it will be called by the `Process` class when preparing command arguments, leading to possible hijacking. This issue has been addressed in release versions 5.4.46, 6.4.14, and 7.1.7. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Affected packages and fixed versions

Source	Package	Fixed in
composer::GitHub Security Advisory Composer	symfony/process, symfony/symfony	5.4.46, 6.4.14, 7.1.7
composer::PHP Security Advisories Database	symfony/process, symfony/symfony	no fix listed

Show all 4 entries from 2 sources

Source	Package	Fixed in
composer::GitHub Security Advisory Composer	symfony/process	5.4.46, 6.4.14, 7.1.7
composer::GitHub Security Advisory Composer	symfony/symfony	5.4.46, 6.4.14, 7.1.7
composer::PHP Security Advisories Database	symfony/process	no fix listed
composer::PHP Security Advisories Database	symfony/symfony	no fix listed

References

What Attestkeep does with this

Inside your cluster, without you opening a spreadsheet.

KnowsThe scanner refreshes its vulnerability database every six hours.

FindsEvery admitted image is rescanned every 24 hours by default (scan.rescanInterval). When Trivy rates this vulnerability critical for the image's package source, it appears in the image's findings by name. Findings without a fix are left out unless includeUnfixed is on.

Tells youA critical_finding event goes to the channels subscribed to it: e-mail, Slack, Teams, a webhook, Jira, GitLab or GitHub.

RefusesWith a policy that blocks critical findings, a pod with this image is refused at admission, a rollback to it included. Pods already running are not evicted.

RecordsEach decision is recorded with the policy that ran and its hash, then sealed under a signed checkpoint.

Try Attestkeep

Read the docs