Findings

CVE-2026-58010

A flaw was found in GLib.

Published Jun 30, 2026 · updated Oct 14, 2026 · gnome glib

A flaw was found in GLib. An off-by-one error can occur in the gvs_tuple_is_normal function in the glib/gvariant-serialiser.c file when doing an alignment padding check because the bounds check uses > instead of >=, causing an out-of-bounds read of only 1 byte. This issue can cause a minor information disclosure of 1 byte and a denial of service when the out-of-bounds read crosses a page boundary.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 30, 2026 · NIST NVD

    Detected

    A flaw was found in GLib. An off-by-one error can occur in the gvs_tuple_is_normal function in the glib/gvariant-serialiser.c file when doing an alignment padding check because the bounds check uses > instead of >=, causing an out-of-bounds read of only 1 byte. This issue can cause a minor information disclosure of 1 byte and a denial of service when the out-of-bounds read crosses a page boundary.

  2. Oct 14, 2026 · NIST NVD

    Updated

    A flaw was found in GLib. An off-by-one error can occur in the gvs_tuple_is_normal function in the glib/gvariant-serialiser.c file when doing an alignment padding check because the bounds check uses > instead of >=, causing an out-of-bounds read of only 1 byte. This issue can cause a minor information disclosure of 1 byte and a denial of service when the out-of-bounds read crosses a page boundary.

Affected

  • cpe gnome/glibversion unspecified
  • cpe gnome/glib2.88.0
  • cpe redhat/enterprise linux10.0
  • cpe redhat/enterprise linux6.0
  • cpe redhat/enterprise linux7.0
  • cpe redhat/enterprise linux8.0
  • cpe redhat/enterprise linux9.0

Sources

  • CVE.orgCVE-2026-58010

    Official CVE identifier

    cve.org
  • FIRST EPSSCVE-2026-58010

    30-day exploitation probability 0.5%

    first.org
  • NIST NVDCVE-2026-58010

    A flaw was found in GLib. An off-by-one error can occur in the gvs_tuple_is_normal function in the glib/gvariant-serialiser.c file when doing an alignment padding check because the bounds check uses > instead of >=, causing an out-of-bounds read of only 1 byte. This issue can cau

    nvd.nist.gov

References