SUSE · Security update for glibc
Affects SUSESource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 7.3 High.
Data as of 10 Nov 2026, 20:06 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 28 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| The GNU C Libraryglibc | Affected
| Fixed in– |
Debiandebian/glibcpkg:deb/debian/glibcOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
This update for glibc fixes the following issues - CVE-2026-5435: unchecked buffer writing in TSIG handling can lead to an out-of-bounds write (bsc#1263656). - CVE-2026-6238: insufficient RDATA length validation can lead to application crashes or uninitialized memory disclosure (bsc#1263658).
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/2026/opensuse-su-2026_21228-1.json (opens in a new tab)
- bugzilla.suse.com/1263656 (opens in a new tab)
- bugzilla.suse.com/1263658 (opens in a new tab)
- suse.com/security/cve/CVE-2026-5435/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-6238/ (opens in a new tab)