CVE-2026-0708
DoS crash in libucl via crafted UCL input with embedded null byte.
Is CVE-2026-0708 being exploited?
Not confirmed. CVE-2026-0708 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.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-0708?
CVE-2026-0708 is rated High with a CVSS score of 8.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-0708?
Yes. A fix has been recorded for CVE-2026-0708. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-0708 affect?
CVE-2026-0708 affects libucl library. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-0708?
Monitor for vendor fixes; update once available
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can crash the host by sending crafted UCL input; segfault in ucl_object_emit causing DoS.
Patch when possible
- affected3e7f023e184e06f30fb5792dacd9dd0f8b692f1b
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.