AAUTHRIZDENTERPRISE AUTHORITY

RESOURCE · AI AUTHORITY

The Developer Didn't Run the Malware. They Viewed a Git Diff.

A DeepSeek-Reasonix command-injection flaw showed how attacker-controlled repository configuration could turn a seemingly benign Git diff into code execution.

The finding

CVE-2026-102437 affects DeepSeek-Reasonix. GitLab's advisory says an attacker controlling repository content, including .gitattributes and local Git configuration, could execute arbitrary commands through the application's workspace-changes diff viewer. Fixed versions are Reasonix 1.39.3 and 2.21.0.

The authority problem

Hostile repositories are not limited to natural-language instructions. Repositories also contain machine-interpreted metadata and configuration. Automatic interpretation cannot be treated as authorization.

Authority to inspect a repository does not imply authority for repository-controlled metadata to invoke a subprocess, network call, write operation or another consequential effect.

The authority-layer answer

An authority layer should normalize the actual effect graph rather than trust the apparent high-level operation. If view diff resolves into read repository, interpret metadata and invoke a process, the material effect change requires re-adjudication before execution.

Machine-interpreted repository content carries no more authority than human-readable repository instructions.

GitHub implication

Coding-agent controls must cover GitHub API effects and consequential local Git effects. A benign read or diff permission should never silently become command-execution authority.

Sources

https://advisories.gitlab.io/npm/reasonix/CVE-2026-102437/

NEXT STEP

Put enterprise authority ahead of consequential action.

Explore the Authority Gap