CVE-2026-10028VulnerabilityPublished 20 Jun 2026Updated 12 Oct 2026

SUSE · Security update for glib-networking

Affects SUSESource GCVE Database

Compare

Authoritative record:CVE-2026-10028· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 May 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 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hat Enterprise Linux 10glib-networking	Affected–	Fixed in–
Red Hat Enterprise Linux 6glib-networking	Affected–	Fixed in–
Red Hat Enterprise Linux 7glib-networking	Affected–	Fixed in–
Red Hat Enterprise Linux 8glib-networking	Affected–	Fixed in–
Red Hat Enterprise Linux 9glib-networking	Affected–	Fixed in–

Description

A security update for glib-networking addresses CVE-2026-10028, a vulnerability where two certificates signed by each other can cause an infinite loop during certificate validation. This issue affects the certificate validation process in glib-networking. No specific affected versions or patch details are provided in the available data. The vulnerability has a medium severity rating and no known exploits in the wild have been reported.

Impact

The vulnerability can cause the certificate validation process to enter an infinite loop when encountering two certificates signed by each other. This may lead to denial of service or disruption in applications relying on glib-networking for certificate validation. There is no evidence of active exploitation in the wild.

Summary

CVE-2026-10028 is a vulnerability in glib-networking involving an infinite loop triggered by two certificates that are signed by each other. This flaw impacts the certificate validation mechanism, potentially causing denial of service or other issues related to certificate processing. The available data does not specify which versions are affected beyond references to glib-networking version 2.80.1 packages from SUSE, nor does it provide explicit patch or remediation information.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Oct 2026, 22:40 UTC

Technical details

References

Community reviews

Related threats