CVE-2026-90484
- Source
- https://cve.org/CVERecord?id=CVE-2026-90484
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90484.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-90484
- Published
- 2026-10-21T12:19:37Z
- Modified
- 2026-10-22T02:48:55Z
- Summary
- Apache bRPC: Null pointer dereference in MySQL reply parser leading to client crash
- Details
-
The MySQL client response parser in Apache bRPC dereferences a null pointer when the server peer sends a zero-payload-length response packet. A response packet whose declared payload length is zero is accepted by the frame-length check (is_full_package), after which the parser reads the response type byte via an unbounded 5-byte fetch that returns nullptr, and type = p[4] dereferences it, crashing the client process.
Root Cause: In brpc::policy::MysqlReply::ConsumePartialIOBuf, buf.fetch(header, 5) returns nullptr when the buffered data only holds the 4-byte header of a zero-length packet, then the code reads p[4] (and, in the fast-auth path, p2[4]) without checking for a null or zero-length packet.
Affected Scenarios: A brpc MySQL client connecting to a malicious or compromised MySQL server (or a MITM) can be crashed by a zero-length server response packet, resulting in denial of service of the client.
Fix: The fix rejects zero-length response packets (returning PARSE_ERROR_ABSOLUTELY_WRONG) both for the initial response type determination and after a fast-auth marker, before reading the type byte. Upgrade to the Apache bRPC version 1.18.0 or apply the PR patch at https://github.com/apache/brpc/pull/3536.
- Database specific
{ "cna_assigner": "apache", "cwe_ids": [ "CWE-476" ], "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90484.json" }- References