CVE-2026-0708: A flaw was found in libucl

Q: How do I fix CVE-2026-0708?

libucl: upgrade to newer than 0.9.4. Exact commands for each OS are on this page.

Q: Is CVE-2026-0708 being exploited?

CVE-2026-0708 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-0708 affect?

CVE-2026-0708 affects libucl. Severity is high (CVSS 8.3). A flaw was found in libucl. A remote attacker could exploit this by providing a specially crafted Universal Configuration Language (UCL) input that contains a key with an embedded null byte. This can cause a segmentation fault (SEGV fault)

Q: How urgent is CVE-2026-0708?

Priority 42/100. High severity; Public exploit reference

This month

HIGH 8.3UPGRADE

CVE-2026-0708 is a high-severity flaw (CVSS 8.3) affecting libucl. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A flaw was found in libucl. A remote attacker could exploit this by providing a specially crafted Universal Configuration Language (UCL) input that contains a key with an embedded null byte. This can cause a segmentation fault (SEGV fault) in the `ucl_object_emit` function when parsing and emitting the object, leading to a Denial of Service (DoS) for the affected system.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.4% (top 67%)
CISA exploited list	No
Weakness	CWE-125
Published	2026-03-17
Last modified	2026-06-17

Publisher (CNA): Fedora Project · Vendor: vstakhov

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-17 04:16 UTCPublished CVE record published
2026-06-17 10:11 UTCUpdated Record last modified

vstakhov libucl UPGRADE

Affected: <= 0.9.4

Fixed in: newer than 0.9.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy libucl || rpm -q libucl || libucl --version

2. UPGRADE to newer than 0.9.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libucl

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libucl

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-0708?

libucl: upgrade to newer than 0.9.4. Exact commands for each OS are on this page.

Is CVE-2026-0708 being exploited?

CVE-2026-0708 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-0708 affect?

CVE-2026-0708 affects libucl. Severity is high (CVSS 8.3). A flaw was found in libucl. A remote attacker could exploit this by providing a specially crafted Universal Configuration Language (UCL) input that contains a key with an embedded null byte. This can cause a segmentation fault (SEGV fault)

How urgent is CVE-2026-0708?

Priority 42/100. High severity; Public exploit reference

Related CVEs

CVE-2025-6499 LOW 3.3 UPGRADE A vulnerability classified as problematic was found in vstakhov libucl up to 0.9.2

References

← Back to latest CVEs