CVE-2026-110634 danday74 CVE debrief

Who should care

Defenders responsible for git-diff deployments, especially in environments processing untrusted input, should assess exposure and prioritize patching or mitigation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure and apply patches or mitigations as available. The critical nature of this vulnerability, with a CVSS score of 9.3, emphasizes the need for proactive verification and

Why it matters

CVE-2026-110634 is a critical OS command injection vulnerability in git-diff before 2.0.7. Defenders should prioritize verifying exposure, especially in environments processing untrusted input, and apply patches or mitigations as available. The vulnerability allows attackers to execute shell commands via crafted input strings to the gitDiff API, potentially leading to code execution with Node.js privileges. Limited information is available on actual exploitation or affected deployments, emphasizing the need for proactive verification and remediation.

• Potential for attackers to execute arbitrary shell commands
• Risk of code execution with Node.js process privileges
• Need for defenders to verify exposure and apply patches
• Importance of monitoring for suspicious git-diff activity

Technical summary

The git-diff package before version 2.0.7 contains an OS command injection vulnerability. Attackers can execute shell commands by supplying crafted strings to the gitDiff API, potentially leading to arbitrary code execution with Node.js process privileges. This vulnerability is critical, with a CVSS score of 9.3, and defenders should prioritize verifying exposure, especially in environments where untrusted input is processed, and apply patches or updates to git-diff as available. The vulnerability allows attackers to execute shell commands via crafted input strings to the gitDiff API, potentially leading to code execution with Node.js privileges.

Defensive priority

Defenders should prioritize verifying exposure of git-diff versions before 2.0.7, especially in environments where untrusted input is processed.

Recommended defensive actions

• Verify git-diff versions in use and compare to the affected version range
• Assess exposure in environments where untrusted input is processed
• Apply patches or updates to git-diff as available
• Monitor for suspicious activity related to git-diff usage
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the OS command injection vulnerability in git-diff before 2.0.7. However, limited information is available on actual exploitation or affected deployments.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.