CVE-2026-49959
RCE in Hermes WebUI via crafted Git config in workspace .git/config
Is CVE-2026-49959 being exploited?
Not confirmed. CVE-2026-49959 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.95% probability of exploitation in the next 30 days.
How severe is CVE-2026-49959?
CVE-2026-49959 is rated High with a CVSS score of 8.7. 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-49959?
Yes. A fix has been recorded for CVE-2026-49959. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-49959 affect?
CVE-2026-49959 affects Hermes WebUI (<0.51.311). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-49959?
Upgrade to 0.51.311+; verify workspace Git config handling
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can run arbitrary commands on the host by manipulating Git config during status/fetch; remote code execution.
Immediate action required
- affected< 0.51.311
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.