Skip to content
Heist/ feed
Back to feed
HighFix available

Apache Thrift, Apache Thrift: WebSocket frame decoders allocate the payload buffer from the declared length, not the bytes received (Node.js, D)

Type: advisorySources: OSV

Memory allocation with excessive size value, Improper handling of length parameter inconsistency vulnerability in Apache Thrift nodejs and D lang bindings. Both bindings' WebSocket server transports read the payload length out of the frame header and allocate that many bytes immediately, without checking that the 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. This issue affects Apache Thrift before 0.25.0. Users are recommended to upgrade to version 0.25.0, which fixes the issue.

Products
thrift
Affected versions
Not specified
Fixed versions
0.25.0
CVEs
CVE-2026-83745
Confirmed fixed CVEs
Not specified
Updated in this feed
28 Oct 2026, 12:32 UTC · Revision 1

Source evidence

Apache Thrift, Apache Thrift: WebSocket frame decoders allocate the payload buffer from the declared length, not the bytes received (Node.js, D)

core-osv · Original source

Published 9 Oct 2026, 10:53 UTC

Memory allocation with excessive size value, Improper handling of length parameter inconsistency vulnerability in Apache Thrift nodejs and D lang bindings. Both bindings' WebSocket server transports read the payload length out of the frame header and allocate that many bytes immediately, without checking that the 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. This issue affects Apache Thrift before 0.25.0. Users are recommended to upgrade to version 0.25.0, which fixes the issue.

osv:BIT-thrift-2026-83745

thrift

Fixed versions: 0.25.0

Complete source record
{
  "id": "9ffdc3a7d348699b4536f9340a425c5363b49b19c3b3e80cda09f25a5c7785d7",
  "url": "https://osv.dev/vulnerability/BIT-thrift-2026-83745",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Apache Thrift, Apache Thrift: WebSocket frame decoders allocate the payload buffer from the declared length, not the bytes received (Node.js, D)",
    "summary": "Memory allocation with excessive size value, Improper handling of length parameter inconsistency vulnerability in Apache Thrift nodejs and D lang bindings. Both bindings' WebSocket server transports read the payload length out of the frame header and allocate that many bytes immediately, without checking that the 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. This issue affects Apache Thrift before 0.25.0. Users are recommended to upgrade to version 0.25.0, which fixes the issue.",
    "evidence": "osv:BIT-thrift-2026-83745",
    "products": [
      {
        "name": {
          "value": "thrift",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "0.25.0",
            "evidence": "/affected/0/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "BIT-thrift-2026-83745",
      "aliases": [
        "BIT-thrift-2026-83745",
        "CVE-2026-83745"
      ],
      "affected": [
        {
          "ranges": [
            {
              "type": "SEMVER",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "0.25.0"
                }
              ]
            }
          ],
          "package": {
            "name": "thrift",
            "purl": "pkg:bitnami/thrift",
            "ecosystem": "Bitnami"
          },
          "severity": [
            {
              "type": "CVSS_V4",
              "score": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
            }
          ],
          "database_specific": {
            "source": "https://github.com/bitnami/vulndb/tree/main/data/thrift/BIT-thrift-2026-83745.json"
          }
        }
      ],
      "modified": "2026-10-09T12:00:13.098423804Z",
      "provider": "osv",
      "references": [
        "https://lists.apache.org/thread/33otcgbqd27wf6qq810q56znzbomnhg1",
        "https://lists.apache.org/thread/64y7f0b89mnq4xoqcn4h26to8kskolgc",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-83745"
      ],
      "provider_metadata": {
        "cpes": [
          "cpe:2.3:a:apache:thrift:*:*:*:*:*:node.js:*:*",
          "cpe:2.3:a:apache:thrift:*:*:*:*:*:d:*:*"
        ],
        "severity": "High"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-83745",
        "evidence": "/aliases"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/database_specific/severity"
  },
  "source_id": "core-osv",
  "document_id": 120703,
  "published_at": "2026-10-09T10:53:00.357+00:00"
}