CVE-2026-75926
Hugo flaw lets malicious Tailwind config execute shell commands during site builds.
Is CVE-2026-75926 being exploited?
Not confirmed. CVE-2026-75926 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.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-75926?
CVE-2026-75926 is rated Critical with a CVSS score of 9.3. 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-75926?
Yes. A fix has been recorded for CVE-2026-75926. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-75926 affect?
CVE-2026-75926 affects Hugo 0.162.0 - 0.164.x, Sites using Hugo asset pipeline with TailwindCSS, Themes/modules/starter templates supplying tailwind.config.js. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-75926?
Upgrade to Hugo >=0.165.0, remove Tailwind from allow-list, and audit themes/CI build pipelines.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary command execution as the account performing the build via malicious tailwind.config.js spawning child processes.
Immediate action required
- affected>= 0.162.0 and < 0.165.0
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.