Skip to main content
CVE-2026-84243VulnerabilityPublished Updated

SUSE · Security update for glibc

Affects SUSESource GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-84243· High 7.0

Not known to be exploited · CVSS 7.0 High.

Data as of 19 Nov 2026, 15:19 UTC

CVSS 3.1 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (glibc)CVSS 3.17.0
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 18 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
The GNU C LibraryglibcAffected
  • >=2.0
Fixed in–
Debiandebian/glibcpkg:deb/debian/glibcOther threatsAffected
  • >=2.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official security update provided by the SUSE Product Security Team to remediate these vulnerabilities. Since this is an official fix, deploying the update will address all listed issues. No additional mitigation steps are indicated.

Description

This security update for glibc addresses multiple vulnerabilities including a reachable assert that can cause process crashes, a directory traversal vulnerability via gettext functions and the LANGUAGE environment variable that can lead to arbitrary code execution, a TOCTOU race condition in the dynamic loader allowing local privilege escalation, and a one-byte out-of-bounds read on Power8 architectures causing program crashes.

References

Community reviews

Loading reviews…