Vulnerability in mysql-5.5 (UBUNTU-CVE-2026-46863)

Summary

Vulnerability in mysql-5.5 (UBUNTU-CVE-2026-46863). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 8.0.46-0ubuntu0.20.04.1+esm3 or later.

Original description

The description as published by the source.

Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: Connection Handling). Supported versions that are affected are MySQL Server: 8.4.0-8.4.9, 9.0.0-9.7.0; MySQL Cluster: 8.0.11-8.0.46, 8.4.0-8.4.9 and 9.0.0-9.7.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Server, MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server, MySQL Cluster. CVSS 3.1 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-46863 has been found in mysql-5.5.
Risk of unauthorized operations or information disclosure.
What to do: upgrade mysql-5.5 to 8.0.46-0ubuntu0.20.04.1+esm3 or later.
If unsure, ask your IT team or search "mysql-5.5 UBUNTU-CVE-2026-46863" on the vendor's site.

UBUNTU-CVE-2026-46863 (mysql-5.5)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 8.0.46-0ubuntu0.20.04.1+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 mysql-5.5.

📍 Affected scope

Check the vendor advisory for the affected versions of mysql-5.5.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 8.0.46-0ubuntu0.20.04.1+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 'mysql-5.5' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

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