ReconXWatchtower

Where this stands

First reported 17/11/2026 12:07

  1. 1Unconfirmednot observed
  2. 2Corroboratednot observed
  3. 3Confirmed now17/11/2026 12:07BSI CERT-Bund (WID)
  4. 4Exploitednot yet

Unconfirmed and Corroborated were never seen on its own: the first report we had was already stronger.

glibc: scanf and ungetwc memory flaws (CVE-2026-5450, CVE-2026-5928) fixed in Debian and Ubuntu updates

GNU libc · Critical (CVSS 9.8)

CVE-2026-5358 CVE-2026-5450 CVE-2026-5928

Published 17/11/2026 13:30

Timeline

2 events over 1 h

  1. 17/11/2026 12:07ConfirmedBSI CERT-Bund (WID)+1 h
  2. 17/11/2026 13:30Published on WatchtowerPro CISO

In short

Three separate glibc CVEs are in the notes. CVE-2026-5450 is a one-byte heap overflow in scanf with %mc (CVSS 9.8). CVE-2026-5928 is an out-of-bounds read in ungetwc (CVSS 7.5). CVE-2026-5358 is a NIS buffer overflow that Red Hat shows as rejected by its CNA; ReconX has no data on it yet. Neither of the first two is on CISA's known-exploited list (checked 17/11/2026).

How bad is it

Critical per BSI CERT-Bund; ratings differ between sources. If an application passes attacker-controlled data to the affected functions, an attacker could corrupt memory, crash the program or manipulate files.

Confirmed by the vendor or a CERT - no exploitation reported yet.

Severity score

9.8of 10Critical

The worst of 3 CVEs · CVSS 3.1 from NVD, from the vendor, read 18/11/2026. CVE-2026-5358: no score published yet.

What an attacker needs

  • Internet access to itEnough
  • A loginNot needed
  • A user to clickNo
  • Special settingsNo

Red helps the attacker, blue holds them back, grey is not published yet.

If it works, an attacker can

  • Read the data it holds
  • Change or delete that data
  • Take it offline

Type: memory corruption.

A score is the worst case for the flaw, not a verdict on any one system. How we score · ReconX customers see which of their own systems are affected.

Affected versions

  • CVE-2026-5450: glibc 2.7 to 2.43, per NVD and Debian. Programs that call the scanf family with %mc and an explicit width above 1024 are exposed.
  • CVE-2026-5928: glibc 2.43 or earlier, per Debian and Ubuntu. It needs a character set where single-byte and multi-byte encodings overlap, which the advisory text says cannot happen in the standard Unicode character sets.
  • CVE-2026-5358: legacy NIS code (nis_local_principal). Red Hat marks this CVE as rejected by the assigning CNA.

What to do now

  • Install the vendor glibc update: Debian 13 2.41-12+deb13u4; Ubuntu 26.04 2.43-2ubuntu2.3, 24.04 2.39-0ubuntu8.8, 22.04 2.35-0ubuntu3.14 (USN-8611-1).
  • On Red Hat systems, check errata RHSA-2026:33126 and RHSA-2026:42733 for the affected RHEL versions.
  • Check whether NIS is used on your hosts. Disable it if it is not needed. This reduces exposure and does not make a server safe.
  • For Debian 12, Debian 11 and Ubuntu 20.04 or older, no fix was found in the sources read. Ask your hosting provider about their status.

ReconX customers see the full notice - and their own systems

Our customers are alerted at every phase. Until a patch exists, the ReconX agent watches their servers from the inside for anomalies, and our outside view - the attacker's view - shows which systems to fix first.

In ReconX: the full analysis, 5 open questions, followed up as sources answer and all 10 sources with their dates. And technology matching: which of your systems run GNU libc, at which version, fixed or not - and what each one needs.

Sign in to ReconXAbout ReconX

Main sources

[UPDATE] [kritisch] GNU libc: Mehrere Schwachstellen CERT · CVE-2026-5358 - Red Hat Customer Portal Research · CVE-2026-5358 - Security Bug Tracker - Debian Research

← All Watchtower notices

Pro CISO publishes ReconX Watchtower notices from public sources so organisations can act early. A notice describes an issue, never any organisation's systems. Times are Amsterdam time. Report a vulnerability in our systems.

ReconX Watchtower opened to the public on 24 October 2026, in the wake of PHP2Shell - our contribution to a safer digital ecosystem.