{
    "dataType": "CVE_RECORD",
    "dataVersion": "5.2",
    "cveMetadata": {
        "cveId": "CVE-2026-90484",
        "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
        "state": "PUBLISHED",
        "assignerShortName": "apache",
        "dateReserved": "2026-09-12T04:06:06.138Z",
        "datePublished": "2026-10-21T12:19:37.796Z",
        "dateUpdated": "2026-10-21T12:19:37.796Z"
    },
    "containers": {
        "cna": {
            "providerMetadata": {
                "orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
                "shortName": "apache",
                "dateUpdated": "2026-10-21T12:19:37.796Z"
            },
            "title": "Apache bRPC: Null pointer dereference in MySQL reply parser leading to client crash",
            "problemTypes": [
                {
                    "descriptions": [
                        {
                            "description": "CWE-476 NULL Pointer Dereference",
                            "lang": "en",
                            "cweId": "CWE-476",
                            "type": "CWE"
                        }
                    ]
                }
            ],
            "source": {
                "discovery": "INTERNAL"
            },
            "affected": [
                {
                    "vendor": "Apache Software Foundation",
                    "product": "Apache bRPC",
                    "packageURL": "pkg:github/apache/brpc",
                    "versions": [
                        {
                            "status": "affected",
                            "version": "<= 1.11.0",
                            "lessThan": "1.18.0",
                            "versionType": "semver"
                        }
                    ],
                    "defaultStatus": "unaffected",
                    "collectionURL": "https://github.com",
                    "packageName": "apache/brpc"
                }
            ],
            "descriptions": [
                {
                    "value": "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.\n\n\n\nRoot 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.\n\n\n\nAffected 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.\n\n\n\nFix: 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.",
                    "lang": "en",
                    "supportingMedia": [
                        {
                            "type": "text/html",
                            "base64": false,
                            "value": "<p>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.</p><p>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.</p><p>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.</p><p>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.</p>"
                        }
                    ]
                }
            ],
            "references": [
                {
                    "url": "https://github.com/apache/brpc/pull/3536",
                    "name": "PR 3536"
                },
                {
                    "url": "https://lists.apache.org/thread/2pf15ojj0vr7rtx95677kgtl1mx3gdgb",
                    "tags": [
                        "vendor-advisory"
                    ]
                }
            ],
            "metrics": [
                {
                    "other": {
                        "type": "Textual description of severity",
                        "content": {
                            "text": "moderate"
                        }
                    },
                    "scenarios": [
                        {
                            "lang": "en",
                            "value": "GENERAL"
                        }
                    ]
                }
            ],
            "x_generator": {
                "engine": "Vulnogram 0.2.0"
            }
        }
    }
}