← Back
USN-8363-1
Vulnerability in mysql-8.0 (USN-8363-1)
Summary
vulnerability in mysql-8.0 (USN-8363-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `8.0.46-0ubuntu0.22.04.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **USN-8363-1** has been found in mysql-8.0.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade mysql-8.0 to **8.0.46-0ubuntu0.22.04.2** or later.
If unsure, ask your IT team or search "mysql-8.0 USN-8363-1" on the vendor's site.
USN-8363-1 (mysql-8.0) —
Patched: `8.0.46-0ubuntu0.22.04.2` — 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 mysql-8.0.
📍 Affected scope
mysql-8.0 — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **8.0.46-0ubuntu0.22.04.2**.
🛡️ 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 'mysql-8.0' .` 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
-
1Identify exposure identify
grep -r 'mysql-8.0' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `mysql-8.0` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade mysql-8.0 to 8.0.46-0ubuntu0.22.04.2ステージング環境で 8.0.46-0ubuntu0.22.04.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:22.04:LTS
mysql-8.0
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.46-0ubuntu0.22.04.2"}]}]
Ubuntu:24.04:LTS
mysql-8.0
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.46-0ubuntu0.24.04.2"}]}]
Ubuntu:25.10
mysql-8.4
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.4.9-0ubuntu0.25.10.1"}]}]
Ubuntu:26.04:LTS
mysql-8.4
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.4.9-0ubuntu0.26.04.1"}]}]
References
- advisory https://ubuntu.com/security/notices/USN-8363-1
- report https://ubuntu.com/security/CVE-2026-21998
- report https://ubuntu.com/security/CVE-2026-22001
- report https://ubuntu.com/security/CVE-2026-22002
- report https://ubuntu.com/security/CVE-2026-22004
- report https://ubuntu.com/security/CVE-2026-22005
- report https://ubuntu.com/security/CVE-2026-22009
- report https://ubuntu.com/security/CVE-2026-22015
- report https://ubuntu.com/security/CVE-2026-22017
- report https://ubuntu.com/security/CVE-2026-34267
- report https://ubuntu.com/security/CVE-2026-34270
- report https://ubuntu.com/security/CVE-2026-34271
- report https://ubuntu.com/security/CVE-2026-34276
- report https://ubuntu.com/security/CVE-2026-34278
- report https://ubuntu.com/security/CVE-2026-34293
- report https://ubuntu.com/security/CVE-2026-34303
- report https://ubuntu.com/security/CVE-2026-34304
- report https://ubuntu.com/security/CVE-2026-34308
- report https://ubuntu.com/security/CVE-2026-34317
- report https://ubuntu.com/security/CVE-2026-34318
- report https://ubuntu.com/security/CVE-2026-34319
- report https://ubuntu.com/security/CVE-2026-35236
- report https://ubuntu.com/security/CVE-2026-35237
- report https://ubuntu.com/security/CVE-2026-35238
- report https://ubuntu.com/security/CVE-2026-35239
- report https://ubuntu.com/security/CVE-2026-35240