# CVE-2026-10028: Denial of service in Red Hat Enterprise Linux 10

> A remote attacker can cause a denial of service via infinite loop in glib-networking when using the GnuTLS backend with circular certificate chains.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 26 Jun 2026
- **Also known as:** AZL-89301, DEBIAN-CVE-2026-10028, ECHO-f55e-6dd0-d4b5, GHSA-qvjg-2vfm-53c7, OESA-2026-2561, SUSE-SU-2026:22102-1, SUSE-SU-2026:22135-1, SUSE-SU-2026:22230-1, SUSE-SU-2026:22297-1, SUSE-SU-2026:2810-1, SUSE-SU-2026:3032-1, SUSE-SU-2026:3121-1, UBUNTU-CVE-2026-10028, openSUSE-SU-2026:11010-1, openSUSE-SU-2026:21130-1

## What is CVE-2026-10028?

CVE-2026-10028 is a medium-severity denial of service vulnerability in Red Hat Enterprise Linux 10, published on 28 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A flaw was found in glib-networking. A remote attacker can exploit this vulnerability by presenting a specially crafted certificate chain to an application that uses glib-networking with the GnuTLS backend enabled and performs certificate verification. This crafted chain, which contains circular issuer relationships, can cause an infinite loop during certificate verification. The unbounded traversal consumes excessive CPU resources, leading to a denial of service for the affected process or worker.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

## Which versions are affected by CVE-2026-10028?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glib-networking` | SUSE:Linux Enterprise Micro 5.3 | All versions | 2.70.1-150400.3.3.1 |
| `glib-networking` | SUSE:Linux Enterprise Micro 5.4 | All versions | 2.70.1-150400.3.3.1 |
| `glib-networking` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.70.1-150400.3.3.1 |
| `glib-networking` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 2.78.0-150600.3.3.1 |
| `glib-networking` | SUSE:Linux Enterprise Server 16.0 | All versions | 2.80.1-160000.3.1 |
| `glib-networking` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.48.2-6.6.1 |
| `glib-networking` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 2.80.1-160000.3.1 |
| `glib-networking` | SUSE:Linux Micro 6.0 | All versions | 2.76.0-4.1 |
| `glib-networking` | SUSE:Linux Micro 6.1 | All versions | 2.78.0-slfo.1.1_2.1 |
| `glib-networking` | SUSE:Linux Micro 6.2 | All versions | 2.80.1-160000.3.1 |
| `glib-networking` | openSUSE:Leap 16.0 | All versions | 2.80.1-160000.3.1 |
| `glib-networking` | openSUSE:Tumbleweed | All versions | 2.80.1-3.1 |

## How do I fix CVE-2026-10028?

Apply the vendor's patch.

## Is CVE-2026-10028 being exploited?

There is no known exploitation of CVE-2026-10028 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10028 and fix it if it is affected.

What it is: CVE-2026-10028 is a medium-severity denial of service vulnerability in Red Hat Enterprise Linux 10, published on 28 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-10028 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10028/ (Markdown: https://insights.sbomify.com/CVE-2026-10028/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10028
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10028
- OSV: https://osv.dev/vulnerability/CVE-2026-10028

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10028/
Summaries are generated and may contain mistakes; the official description above is the record.