{
  "containers": {
    "cna": {
      "providerMetadata": {
        "orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09"
      },
      "title": "WebSocket frame decoders allocate the payload buffer from the declared length, not the bytes received (Node.js, D)",
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "CWE-789 Memory allocation with excessive size value",
              "lang": "en",
              "cweId": "CWE-789",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "description": "CWE-130 Improper handling of length parameter inconsistency",
              "lang": "en",
              "cweId": "CWE-130",
              "type": "CWE"
            }
          ]
        }
      ],
      "source": {
        "discovery": "EXTERNAL"
      },
      "affected": [
        {
          "vendor": "Apache Software Foundation",
          "product": "Apache Thrift",
          "packageURL": "pkg:npm/thrift",
          "versions": [
            {
              "status": "affected",
              "version": "0",
              "lessThan": "0.25.0",
              "versionType": "semver"
            }
          ],
          "defaultStatus": "unaffected"
        },
        {
          "vendor": "Apache Software Foundation",
          "product": "Apache Thrift",
          "packageName": "D language bindings",
          "versions": [
            {
              "status": "affected",
              "version": "0",
              "lessThan": "0.25.0",
              "versionType": "semver"
            }
          ],
          "defaultStatus": "unaffected"
        }
      ],
      "descriptions": [
        {
          "value": "Memory allocation with excessive size value, Improper handling of length parameter inconsistency vulnerability in Apache Thrift\u00a0\nnodejs and D lang bindings.\n\nBoth bindings' WebSocket server transports read the payload length out of the\u00a0frame header and allocate that many bytes immediately, without checking that the\u00a0bytes have arrived. A single ~14-byte frame therefore commits as much memory as it cares to declare -- measured at 513 MiB against the Node.js server and 2 GiB against the D transport -- and in the Node.js case the connection is left open afterwards, so the frame can simply be sent again.\n\n\n\n\nThis issue affects Apache Thrift before 0.25.0.\n\n\n\nUsers are recommended to upgrade to version 0.25.0, which fixes the issue.",
          "lang": "en",
          "supportingMedia": [
            {
              "type": "text/html",
              "base64": false,
              "value": "<p>Memory allocation with excessive size value, Improper handling of length parameter inconsistency vulnerability in Apache Thrift&nbsp;\nnodejs and D lang bindings.<br><br>Both bindings' WebSocket server transports read the payload length out of the&nbsp;frame header and allocate that many bytes immediately, without checking that the&nbsp;bytes have arrived. A single ~14-byte frame therefore commits as much memory as it cares to declare -- measured at 513 MiB against the Node.js server and 2 GiB against the D transport -- and in the Node.js case the connection is left open afterwards, so the frame can simply be sent again.<br></p><p>This issue affects Apache Thrift before 0.25.0.</p><p>Users are recommended to upgrade to version 0.25.0, which fixes the issue.</p>"
            }
          ]
        }
      ],
      "references": [
        {
          "url": "https://lists.apache.org/thread/33otcgbqd27wf6qq810q56znzbomnhg1",
          "tags": [
            "vendor-advisory"
          ]
        },
        {
          "url": "https://lists.apache.org/thread/64y7f0b89mnq4xoqcn4h26to8kskolgc",
          "tags": [
            "vendor-advisory"
          ]
        }
      ],
      "metrics": [
        {
          "other": {
            "type": "Textual description of severity",
            "content": {
              "text": "important"
            }
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ],
          "format": "CVSS",
          "cvssV4_0": {
            "attackVector": "NETWORK",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "privilegesRequired": "NONE",
            "userInteraction": "NONE",
            "vulnConfidentialityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "vulnAvailabilityImpact": "HIGH",
            "subAvailabilityImpact": "NONE",
            "exploitMaturity": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "valueDensity": "NOT_DEFINED",
            "vulnerabilityResponseEffort": "NOT_DEFINED",
            "providerUrgency": "NOT_DEFINED",
            "version": "4.0",
            "baseSeverity": "HIGH",
            "baseScore": 8.7,
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
          }
        }
      ],
      "credits": [
        {
          "lang": "en",
          "value": "Ho1aAs <xxy010605@gmail.com> for Node.js",
          "type": "finder"
        },
        {
          "lang": "en",
          "value": "Apache Thrift Developers for D language",
          "type": "finder"
        }
      ],
      "x_generator": {
        "engine": "Vulnogram 1.0.3"
      }
    }
  },
  "cveMetadata": {
    "cveId": "CVE-2026-83745",
    "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
    "serial": 1,
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.0"
}