Cognition Open-Sources Devin Vulnerability-Fixes Plugin: Three Critical Flaws in One Pass

What happened

The plugin contains three skills — fix-php-vuln, fix-node-vuln and fix-gitlab-vuln — with source code on GitHub under the MIT license. Cognition packaged its internal remediation workflow as these skills: a read-only inventory first, then an approval gate, verification, edits, and finally tests plus a pull request, aiming to cover as many repositories as possible in one pass.

Each flaw has its own advisory: PHP2Shell covers two severe PHP remote-code-execution flaws, CVE-2026-109618 and CVE-2026-109619; the Node.js Oct 21 security release fixes 10 CVEs, four rated High, led by the Brotli decoder flaw CVE-2026-111497 that can enable remote code execution; GitLab's CVE-2026-110264 is an integer overflow in the regular-expression compiler scoring CVSS 10.0, allowing unauthenticated code execution.

The plugin runs beyond Devin: any coding agent that reads SKILL.md files can use it, including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and Windsurf. Installation is via the Devin plugin marketplace or the npx skills command; running it needs git, a shell, Docker and registry access, and the npx install path requires Node.js 22.20 or later.

Key facts

1. The plugin is called Devin Vulnerability Fixes: three skills — fix-php-vuln, fix-node-vuln and fix-gitlab-vuln — open-sourced under MIT in the CognitionAI/devin-vuln-fixes repository.
2. PHP2Shell fixed versions are 8.2.35, 8.3.36, 8.4.27 and 8.5.12; PHP 8.1 and older get no official releases, only source backports for 7.4, 8.0 and 8.1, and PHP itself says every web-serving setup is at risk.
3. The Node.js Oct 21 security release fixes 10 CVEs, four rated High; fixed versions are 22.23.4, 24.22.1 and 26.12.1; Node.js 20 and older are end-of-life with no fix.
4. GitLab CVE-2026-110264 affects GitLab CE/EE from version 7.0 onward at CVSS 10.0; GitLab.com and GitLab Dedicated are already patched, while self-managed deployments need their own upgrade.
5. The five-step flow: read-only inventory, approval gate, official-source verification of versions and checksums, before-and-after testing, and one pull request per repository; managed runtimes, appliances and Electron apps are flagged, not patched; no fix-rate benchmark is published, so results depend on test coverage.