On this page (7 sections)

On 12 November 2026 Ubuntu published USN-9065-1, a security notice covering several vulnerabilities in the GNU C Library (glibc), the core C library that nearly every program on a Linux server uses. The fix ships as updated libc6 packages for Ubuntu 22.04 LTS, 24.04 LTS, 26.04 LTS and 26.10.

If you run Ubuntu web servers, containers built on Ubuntu images, or shared hosting boxes with local users, this update belongs in your next patch window. The three CVEs with published records are rated medium and need local access or the local network. The sources do not state the attack vector for the other four, so whether they can be reached remotely is unconfirmed. Because glibc sits under everything, the update is worth doing promptly.

What the notice covers

Ubuntu lists seven CVEs in this one notice. Its advisory text describes them as follows:

Issues listed in USN-9065-1, as described by Ubuntu
CVEComponentDescribed impact
CVE-2026-18374fopen, ccs= optionCrash or possible arbitrary code execution
CVE-2026-8674DNS search list handlingCrash (denial of service) by an attacker on the local network
CVE-2026-86805Dynamic loader, $ORIGIN in setuid/setgid programsLocal attacker could possibly run code with elevated privileges
CVE-2026-95818Dynamic loader, $ORIGIN expansionStack-based buffer overflow; crash or information disclosure by a local attacker
CVE-2026-89092nscd serviceCrash from large DNS responses (denial of service)
CVE-2026-97399strncasecmp optimized for Power8Crash (denial of service)
CVE-2026-84243gettext, LANGUAGE variableLocal attacker could possibly load message catalogs from arbitrary locations and execute code

The sources provide scores and technical write-ups only for the first three. For the other four, this article relies on Ubuntu's one-line descriptions, which do not give a CVSS score. Check the CVE records for details before judging their priority.

Technical details of the three scored flaws

CVE-2026-18374: heap overflow in fopen (CVSS 4.9)

Per the GitHub advisory, passing an effectively empty string to the ,ccs= extension of the fopen mode argument in glibc 2.45 or earlier may cause a heap buffer overflow when the mode string is attacker controlled (CWE-787). The advisory notes this usage pattern is not seen in applications in common GNU/Linux distributions, and that applications handling user-supplied ccs values should validate them first. The score of 4.9 reflects a local attack vector and high attack complexity.

CVE-2026-8674: DNS search list assertion failure (CVSS 5.3)

In glibc 2.26 to 2.44, loading a resolver configuration from /etc/resolv.conf or the LOCALDOMAIN variable with a search domain of roughly 200 characters or more triggers an assertion failure that aborts the process (GitHub advisory). The truncation check compared against the wrong size. Because search domains are often written to resolv.conf from DHCP or VPN data, an attacker on the local network may be able to trigger it without privileges, subject to validation by the network configuration software. Long-running processes that reload resolv.conf on the next query are affected too. The impact is availability only (CWE-617, adjacent attack vector).

CVE-2026-86805: ld.so race condition (CVSS 6.3)

In glibc 2.14 through 2.44, a time-of-check to time-of-use race in the dynamic loader can let a local attacker escalate privileges when $ORIGIN is expanded in DT_RPATH for setuid/setgid programs (GitHub advisory). It requires the fs.protected_hardlinks sysctl to be disabled, an installed setuid or setgid binary with a specific RPATH pattern, and winning a race. The advisory states that major Linux distributions ship with fs.protected_hardlinks enabled by default, which mitigates it.

The CVE records give version ranges such as 2.45 or earlier and 2.14 to 2.44 for upstream glibc. Ubuntu backports fixes, so use the Ubuntu package versions below, not the upstream version number, to decide whether a system is patched.

Who is realistically exposed

  • Multi-user servers, shared hosting and CI runners where untrusted local users can run code. These matter most for the local privilege escalation items.
  • Laptops, VMs and servers that take DNS search domains from DHCP or a VPN on a network you do not fully control (CVE-2026-8674).
  • Systems running the nscd service, since Ubuntu describes a crash from large DNS responses (CVE-2026-89092). The sources do not say how an attacker would reach it.
  • Containers and images based on Ubuntu 22.04, 24.04, 26.04 or 26.10. The libc6 package inside the image needs the update, and patching the host does not change it.
  • Single-purpose web servers with no local untrusted users face lower practical risk, but still run glibc in every process and should patch.

How to check your exposure

This read-only command shows the installed libc6 version on Ubuntu. Compare the output with the fixed versions in the table below.

Show the installed libc6 version (Ubuntu)Shell
dpkg -l libc6 | grep ^ii
Fixed libc6 versions per Ubuntu release (USN-9065-1)
Ubuntu releaseFixed libc6 version
26.102.44-1ubuntu2.1
26.04 LTS2.43-2ubuntu2.7
24.04 LTS2.39-0ubuntu8.12
22.04 LTS2.35-0ubuntu3.18

To see whether the hardlink protection that mitigates CVE-2026-86805 is on, read the sysctl. A value of 1 means enabled.

Read the hardlink protection setting (Linux)Shell
sysctl fs.protected_hardlinks

What to do now

  1. Inventory Ubuntu hosts, VMs and container base images, and note which release each runs.
  2. Run the version check above and compare it with the fixed libc6 versions.
  3. Apply the update with the standard package manager, as Ubuntu says a normal system update makes the needed changes.
  4. Restart services and long-running processes that still use the old library, or reboot the host in a planned window.
  5. Rebuild and redeploy container images from an updated Ubuntu base.
  6. Confirm fs.protected_hardlinks is 1 on every host, and investigate any host where it is 0.
  7. Re-run the version check afterward and record the result.

This command refreshes the package index and upgrades only libc6 on Ubuntu. Afterward, re-run the version check and confirm it matches the table.

Update libc6 (Ubuntu)Shell
sudo apt update
sudo apt install --only-upgrade libc6
Caution. glibc is loaded by almost every process. Processes keep using the old library until they restart, and a reboot is the simplest way to be sure. Schedule it for production systems and test on a staging host first.

Detection and monitoring afterward

There is no published indicator of exploitation in the sources, so focus on hygiene. Watch for unexpected process aborts with assertion messages after DHCP or VPN changes, which could point to the DNS search list issue. Review setuid and setgid binaries on multi-user hosts and audit for unexpected hard links to them. Keep unattended security updates enabled so future libc6 fixes land quickly.

Patching the operating system does not cover what runs on top of it. A security scan of your verified website can help you spot exposed services and outdated components, and certificate and DNS change monitoring adds visibility between patch cycles. Neither replaces updating libc6.

Tip. For broader habits that keep servers current, see our small business website security guide and the website hacked: what to do guide in case you suspect a compromise.

Timeline

  • 27 August 2026: CVE-2026-18374 published.
  • 17 September 2026: CVE-2026-8674 published.
  • 22 September 2026: CVE-2026-86805 published.
  • 12 November 2026: Ubuntu releases USN-9065-1 with fixed libc6 packages.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-18374 - GitHub Advisory Databasegithub.com
  2. CVE-2026-8674 - GitHub Advisory Databasegithub.com
  3. CVE-2026-86805 - GitHub Advisory Databasegithub.com
  4. USN-9065-1: GNU C Library vulnerabilities | Ubuntu security notices | Ubuntuubuntu.com ·
  • Ubuntu
  • glibc
  • USN
  • Linux
  • patching