Vulnerability in gnutls28 (USN-8502-1)

Summary

vulnerability in gnutls28 (USN-8502-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `3.4.10-4ubuntu1.9+esm3` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **USN-8502-1** has been found in gnutls28. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade gnutls28 to **3.4.10-4ubuntu1.9+esm3** or later. If unsure, ask your IT team or search "gnutls28 USN-8502-1" on the vendor's site.

USN-8502-1 (gnutls28) — Patched: `3.4.10-4ubuntu1.9+esm3` — apply immediately Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

**A vulnerability** (unclassified) exists in gnutls28.

📍 Affected scope

gnutls28 — .

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **3.4.10-4ubuntu1.9+esm3**.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'gnutls28' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'gnutls28' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `gnutls28` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade gnutls28 to 3.4.10-4ubuntu1.9+esm3
```
ステージング環境で 3.4.10-4ubuntu1.9+esm3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:16.04:LTS gnutls28

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.4.10-4ubuntu1.9+esm3"}]}]

Ubuntu:Pro:18.04:LTS gnutls28

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.18-1ubuntu1.6+esm3"}]}]

Ubuntu:Pro:20.04:LTS gnutls28

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.6.13-2ubuntu1.12+esm2"}]}]

References

advisory https://ubuntu.com/security/notices/USN-8502-1
report https://ubuntu.com/security/CVE-2024-0553
report https://ubuntu.com/security/CVE-2024-12243
report https://ubuntu.com/security/CVE-2025-9820
report https://ubuntu.com/security/CVE-2025-14831
report https://ubuntu.com/security/CVE-2026-3833
report https://ubuntu.com/security/CVE-2026-5260
report https://ubuntu.com/security/CVE-2026-33845
report https://ubuntu.com/security/CVE-2026-33846
report https://ubuntu.com/security/CVE-2026-42009
report https://ubuntu.com/security/CVE-2026-42010