CVE-2026-67623
RCE via malicious .git/config fsmonitor when Vibe runs git status.
Is CVE-2026-67623 being exploited?
Not confirmed. CVE-2026-67623 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.53% probability of exploitation in the next 30 days.
How severe is CVE-2026-67623?
CVE-2026-67623 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67623?
Yes. A fix has been recorded for CVE-2026-67623. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67623 affect?
CVE-2026-67623 affects Mistral Vibe <2.23.3, Vibe CLI, Repositories with malicious .git/config fsmonitor. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67623?
Upgrade Vibe to >=2.23.3; avoid running CLI in untrusted repos and audit .git/config files.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can execute arbitrary commands as the user by supplying a repo with a malicious core.fsmonitor entry triggered by Vibe's git status --porcelain.
Immediate action required
- affected< 2.23.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.