Vulnerability-Lookup

CVE-2026-124279 (GCVE-0-2026-124279)

Vulnerability from cvelistv5 – Published: 2026-11-13 16:18 – Updated: 2026-11-13 19:32

Title

Streaming request body limit enforced only after an 8 MB read in elixir-grpc grpc_server

Summary

Allocation of Resources Without Limits or Throttling vulnerability in elixir-grpc grpc_server allows unauthenticated attackers to exhaust server memory via client-streaming or bidirectional-streaming requests. The streaming read clause of GRPC.Server.Adapters.Cowboy.Handler.info/3 (grpc_server/lib/grpc/server/adapters/cowboy/handler.ex) asks Cowboy for up to 8,000,000 bytes per read and compares the running total with max_body_size only after the read returns. The gRPC length prefix of a message is not checked before the message is buffered. Each stream can therefore buffer up to one full read beyond the configured limit before it is refused, and many concurrent streams exhaust node memory. Releases before 1.0.6 apply no limit to streaming requests at all. This issue affects grpc_server: from 1.0.0 before 1.1.0.

Severity

8.2 (High)


                        
                          CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

SSVC

Exploitation: none Automatable: no Technical Impact: partial

CISA Coordinator · CISA-ADP (v2.0.3)

Decision recorded 2026-11-13 17:55 UTC

CWE

CWE-770 - Allocation of Resources Without Limits or Throttling

Assigner

EEF CNA under the mitre root

CNA scorecard A 97/100 over 357 records in the last 180 days details

References

5 references

URL	Tags
https://github.com/elixir-grpc/grpc/security/advi…	vendor-advisoryrelated
https://cna.erlef.org/cves/CVE-2026-124279.html	related
https://osv.dev/vulnerability/EEF-CVE-2026-124279	related
https://github.com/elixir-grpc/grpc/commit/49e18c…	related
https://github.com/elixir-grpc/grpc/commit/b1e771…	patch

Impacted products

2 products

Vendor	Product	Version	CPE status
elixir-grpc	grpc_server	Affected: 1.0.0 , < 1.1.0 (semver) cpe:2.3:a:elixir-grpc:grpc_server::::::::
elixir-grpc	grpc_server	Affected: 49e18c3ec6bb9afe2f712caad3dbab5c56a68a00 , < b1e771d558941b1ed4b6de8b39f6a5375543db01 (git) cpe:2.3:a:elixir-grpc:grpc_server::::::::

Credits

Alfie Goh Li Heng Alfie Goh Li Heng Paulo Valente Peter Ullrich Jonatan Männchen / EEF

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-124279",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-13T17:55:00.516542Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-13T19:32:24.719Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "collectionURL": "https://repo.hex.pm",
          "cpes": [
            "cpe:2.3:a:elixir-grpc:grpc_server:*:*:*:*:*:*:*:*"
          ],
          "defaultStatus": "unaffected",
          "modules": [
            "\u0027Elixir.GRPC.Server.Adapters.Cowboy.Handler\u0027",
            "\u0027Elixir.GRPC.Server.Adapters.Cowboy\u0027"
          ],
          "packageName": "grpc_server",
          "packageURL": "pkg:hex/grpc_server",
          "product": "grpc_server",
          "programFiles": [
            "lib/grpc/server/adapters/cowboy/handler.ex",
            "lib/grpc/server/adapters/cowboy.ex"
          ],
          "programRoutines": [
            {
              "name": "\u0027Elixir.GRPC.Server.Adapters.Cowboy.Handler\u0027:info/3"
            },
            {
              "name": "\u0027Elixir.GRPC.Server.Adapters.Cowboy\u0027:reading_stream/1"
            }
          ],
          "repo": "https://github.com/elixir-grpc/grpc",
          "vendor": "elixir-grpc",
          "versions": [
            {
              "lessThan": "1.1.0",
              "status": "affected",
              "version": "1.0.0",
              "versionType": "semver"
            }
          ]
        },
        {
          "collectionURL": "https://github.com",
          "cpes": [
            "cpe:2.3:a:elixir-grpc:grpc_server:*:*:*:*:*:*:*:*"
          ],
          "defaultStatus": "unaffected",
          "modules": [
            "\u0027Elixir.GRPC.Server.Adapters.Cowboy.Handler\u0027",
            "\u0027Elixir.GRPC.Server.Adapters.Cowboy\u0027"
          ],
          "packageName": "elixir-grpc/grpc",
          "packageURL": "pkg:github/elixir-grpc/grpc",
          "product": "grpc_server",
          "programFiles": [
            "grpc_server/lib/grpc/server/adapters/cowboy/handler.ex",
            "grpc_server/lib/grpc/server/adapters/cowboy.ex"
          ],
          "programRoutines": [
            {
              "name": "\u0027Elixir.GRPC.Server.Adapters.Cowboy.Handler\u0027:info/3"
            },
            {
              "name": "\u0027Elixir.GRPC.Server.Adapters.Cowboy\u0027:reading_stream/1"
            }
          ],
          "repo": "https://github.com/elixir-grpc/grpc",
          "vendor": "elixir-grpc",
          "versions": [
            {
              "lessThan": "b1e771d558941b1ed4b6de8b39f6a5375543db01",
              "status": "affected",
              "version": "49e18c3ec6bb9afe2f712caad3dbab5c56a68a00",
              "versionType": "git"
            }
          ]
        }
      ],
      "configurations": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eThe server must expose at least one client-streaming or bidirectional-streaming RPC method.\u003c/p\u003e"
            },
            {
              "base64": false,
              "type": "text/markdown",
              "value": "The server must expose at least one client-streaming or bidirectional-streaming RPC method."
            }
          ],
          "value": "The server must expose at least one client-streaming or bidirectional-streaming RPC method."
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:elixir-grpc:grpc_server:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "1.1.0",
                  "versionStartIncluding": "1.0.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ],
          "operator": "AND"
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "Alfie Goh Li Heng"
        },
        {
          "lang": "en",
          "type": "finder",
          "value": "Alfie Goh Li Heng"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Paulo Valente"
        },
        {
          "lang": "en",
          "type": "coordinator",
          "value": "Peter Ullrich"
        },
        {
          "lang": "en",
          "type": "coordinator",
          "value": "Jonatan M\u00e4nnchen / EEF"
        }
      ],
      "dateAssigned": "2026-11-13T11:19:13.000Z",
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eAllocation of Resources Without Limits or Throttling vulnerability in elixir-grpc grpc_server allows unauthenticated attackers to exhaust server memory via client-streaming or bidirectional-streaming requests.\u003c/p\u003e\n\u003cp\u003eThe streaming read clause of \u003ccode\u003eGRPC.Server.Adapters.Cowboy.Handler.info/3\u003c/code\u003e (\u003ccode\u003egrpc_server/lib/grpc/server/adapters/cowboy/handler.ex\u003c/code\u003e) asks Cowboy for up to 8,000,000 bytes per read and compares the running total with \u003ccode\u003emax_body_size\u003c/code\u003e only after the read returns. The gRPC length prefix of a message is not checked before the message is buffered. Each stream can therefore buffer up to one full read beyond the configured limit before it is refused, and many concurrent streams exhaust node memory. Releases before 1.0.6 apply no limit to streaming requests at all.\u003c/p\u003e\n\u003cp\u003eThis issue affects grpc_server: from 1.0.0 before 1.1.0.\u003c/p\u003e"
            },
            {
              "base64": false,
              "type": "text/markdown",
              "value": "Allocation of Resources Without Limits or Throttling vulnerability in elixir-grpc grpc_server allows unauthenticated attackers to exhaust server memory via client-streaming or bidirectional-streaming requests.\n\nThe streaming read clause of `GRPC.Server.Adapters.Cowboy.Handler.info/3` (`grpc_server/lib/grpc/server/adapters/cowboy/handler.ex`) asks Cowboy for up to 8,000,000 bytes per read and compares the running total with `max_body_size` only after the read returns. The gRPC length prefix of a message is not checked before the message is buffered. Each stream can therefore buffer up to one full read beyond the configured limit before it is refused, and many concurrent streams exhaust node memory. Releases before 1.0.6 apply no limit to streaming requests at all.\n\nThis issue affects grpc_server: from 1.0.0 before 1.1.0."
            }
          ],
          "value": "Allocation of Resources Without Limits or Throttling vulnerability in elixir-grpc grpc_server allows unauthenticated attackers to exhaust server memory via client-streaming or bidirectional-streaming requests.\n\nThe streaming read clause of GRPC.Server.Adapters.Cowboy.Handler.info/3 (grpc_server/lib/grpc/server/adapters/cowboy/handler.ex) asks Cowboy for up to 8,000,000 bytes per read and compares the running total with max_body_size only after the read returns. The gRPC length prefix of a message is not checked before the message is buffered. Each stream can therefore buffer up to one full read beyond the configured limit before it is refused, and many concurrent streams exhaust node memory. Releases before 1.0.6 apply no limit to streaming requests at all.\n\nThis issue affects grpc_server: from 1.0.0 before 1.1.0."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-130",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "\u003cp\u003eAn unauthenticated client that opens many streaming calls can make the server buffer more request data than its configured limit allows and crash the node, taking down every service on it.\u003c/p\u003e"
                },
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "An unauthenticated client that opens many streaming calls can make the server buffer more request data than its configured limit allows and crash the node, taking down every service on it."
                }
              ],
              "value": "An unauthenticated client that opens many streaming calls can make the server buffer more request data than its configured limit allows and crash the node, taking down every service on it."
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 8.2,
            "baseSeverity": "HIGH",
            "privilegesRequired": "NONE",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "HIGH",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "NONE",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-770",
              "description": "CWE-770 Allocation of Resources Without Limits or Throttling",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T16:18:56.700Z",
        "orgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
        "shortName": "EEF"
      },
      "references": [
        {
          "name": "Streaming request body limit enforced only after an 8 MB read in elixir-grpc grpc_server",
          "tags": [
            "vendor-advisory",
            "related"
          ],
          "url": "https://github.com/elixir-grpc/grpc/security/advisories/GHSA-736x-r87j-jhcm"
        },
        {
          "name": "EEF CNA record for CVE-2026-124279",
          "tags": [
            "related"
          ],
          "url": "https://cna.erlef.org/cves/CVE-2026-124279.html"
        },
        {
          "name": "OSV record EEF-CVE-2026-124279",
          "tags": [
            "related"
          ],
          "url": "https://osv.dev/vulnerability/EEF-CVE-2026-124279"
        },
        {
          "name": "Introducing commit 49e18c3 in elixir-grpc/grpc",
          "tags": [
            "related"
          ],
          "url": "https://github.com/elixir-grpc/grpc/commit/49e18c3ec6bb9afe2f712caad3dbab5c56a68a00"
        },
        {
          "name": "Fix commit b1e771d in elixir-grpc/grpc",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/elixir-grpc/grpc/commit/b1e771d558941b1ed4b6de8b39f6a5375543db01"
        }
      ],
      "source": {
        "discovery": "EXTERNAL"
      },
      "title": "Streaming request body limit enforced only after an 8 MB read in elixir-grpc grpc_server",
      "x_technicalAnalysis": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003e\u003cstrong\u003e1. Large reads\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003easync_read_body/2\u003c/code\u003e asks Cowboy for up to 8,000,000 bytes per read on the streaming path, whatever \u003ccode\u003emax_body_size\u003c/code\u003e is set to.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003e2. The limit is checked after the read\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003etrack_body_bytes/2\u003c/code\u003e adds each returned chunk to a running total and refuses the stream with \u003ccode\u003eRESOURCE_EXHAUSTED\u003c/code\u003e only once the total exceeds \u003ccode\u003emax_body_size\u003c/code\u003e. By then the whole chunk is in memory.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003e3. No check on the length prefix\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eThe 5-byte gRPC prefix can declare up to 4 GiB. The server does not compare it with any limit before buffering, so a prefix that declares an oversized message does not stop the read.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003e4. Result\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eEach client-streaming or bidirectional-streaming call can make the server hold several megabytes more than the configured limit, and the attacker can open many such calls at once. Before 1.0.6 the streaming path had no limit, and \u003ccode\u003eGRPC.Server.Adapters.Cowboy.reading_stream/1\u003c/code\u003e buffered the whole body.\u003c/p\u003e"
            },
            {
              "base64": false,
              "type": "text/markdown",
              "value": "**1. Large reads**\n\n`async_read_body/2` asks Cowboy for up to 8,000,000 bytes per read on the streaming path, whatever `max_body_size` is set to.\n\n**2. The limit is checked after the read**\n\n`track_body_bytes/2` adds each returned chunk to a running total and refuses the stream with `RESOURCE_EXHAUSTED` only once the total exceeds `max_body_size`. By then the whole chunk is in memory.\n\n**3. No check on the length prefix**\n\nThe 5-byte gRPC prefix can declare up to 4 GiB. The server does not compare it with any limit before buffering, so a prefix that declares an oversized message does not stop the read.\n\n**4. Result**\n\nEach client-streaming or bidirectional-streaming call can make the server hold several megabytes more than the configured limit, and the attacker can open many such calls at once. Before 1.0.6 the streaming path had no limit, and `GRPC.Server.Adapters.Cowboy.reading_stream/1` buffered the whole body."
            }
          ],
          "value": "1. Large reads\n\nasync_read_body/2 asks Cowboy for up to 8,000,000 bytes per read on the streaming path, whatever max_body_size is set to.\n\n2. The limit is checked after the read\n\ntrack_body_bytes/2 adds each returned chunk to a running total and refuses the stream with RESOURCE_EXHAUSTED only once the total exceeds max_body_size. By then the whole chunk is in memory.\n\n3. No check on the length prefix\n\nThe 5-byte gRPC prefix can declare up to 4 GiB. The server does not compare it with any limit before buffering, so a prefix that declares an oversized message does not stop the read.\n\n4. Result\n\nEach client-streaming or bidirectional-streaming call can make the server hold several megabytes more than the configured limit, and the attacker can open many such calls at once. Before 1.0.6 the streaming path had no limit, and GRPC.Server.Adapters.Cowboy.reading_stream/1 buffered the whole body."
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
    "assignerShortName": "EEF",
    "cveId": "CVE-2026-124279",
    "datePublished": "2026-11-13T16:18:56.700Z",
    "dateReserved": "2026-11-13T11:18:43.141Z",
    "dateUpdated": "2026-11-13T19:32:24.719Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "collectionURL": "https://repo.hex.pm",
                "cpes": [
                  "cpe:2.3:a:elixir-grpc:grpc_server:*:*:*:*:*:*:*:*"
                ],
                "defaultStatus": "unaffected",
                "modules": [
                  "\u0027Elixir.GRPC.Server.Adapters.Cowboy.Handler\u0027",
                  "\u0027Elixir.GRPC.Server.Adapters.Cowboy\u0027"
                ],
                "packageName": "grpc_server",
                "packageURL": "pkg:hex/grpc_server",
                "product": "grpc_server",
                "programFiles": [
                  "lib/grpc/server/adapters/cowboy/handler.ex",
                  "lib/grpc/server/adapters/cowboy.ex"
                ],
                "programRoutines": [
                  {
                    "name": "\u0027Elixir.GRPC.Server.Adapters.Cowboy.Handler\u0027:info/3"
                  },
                  {
                    "name": "\u0027Elixir.GRPC.Server.Adapters.Cowboy\u0027:reading_stream/1"
                  }
                ],
                "repo": "https://github.com/elixir-grpc/grpc",
                "vendor": "elixir-grpc",
                "versions": [
                  {
                    "lessThan": "1.1.0",
                    "status": "affected",
                    "version": "1.0.0",
                    "versionType": "semver"
                  }
                ]
              },
              {
                "collectionURL": "https://github.com",
                "cpes": [
                  "cpe:2.3:a:elixir-grpc:grpc_server:*:*:*:*:*:*:*:*"
                ],
                "defaultStatus": "unaffected",
                "modules": [
                  "\u0027Elixir.GRPC.Server.Adapters.Cowboy.Handler\u0027",
                  "\u0027Elixir.GRPC.Server.Adapters.Cowboy\u0027"
                ],
                "packageName": "elixir-grpc/grpc",
                "packageURL": "pkg:github/elixir-grpc/grpc",
                "product": "grpc_server",
                "programFiles": [
                  "grpc_server/lib/grpc/server/adapters/cowboy/handler.ex",
                  "grpc_server/lib/grpc/server/adapters/cowboy.ex"
                ],
                "programRoutines": [
                  {
                    "name": "\u0027Elixir.GRPC.Server.Adapters.Cowboy.Handler\u0027:info/3"
                  },
                  {
                    "name": "\u0027Elixir.GRPC.Server.Adapters.Cowboy\u0027:reading_stream/1"
                  }
                ],
                "repo": "https://github.com/elixir-grpc/grpc",
                "vendor": "elixir-grpc",
                "versions": [
                  {
                    "lessThan": "b1e771d558941b1ed4b6de8b39f6a5375543db01",
                    "status": "affected",
                    "version": "49e18c3ec6bb9afe2f712caad3dbab5c56a68a00",
                    "versionType": "git"
                  }
                ]
              }
            ],
            "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "Allocation of Resources Without Limits or Throttling vulnerability in elixir-grpc grpc_server allows unauthenticated attackers to exhaust server memory via client-streaming or bidirectional-streaming requests.\n\nThe streaming read clause of GRPC.Server.Adapters.Cowboy.Handler.info/3 (grpc_server/lib/grpc/server/adapters/cowboy/handler.ex) asks Cowboy for up to 8,000,000 bytes per read and compares the running total with max_body_size only after the read returns. The gRPC length prefix of a message is not checked before the message is buffered. Each stream can therefore buffer up to one full read beyond the configured limit before it is refused, and many concurrent streams exhaust node memory. Releases before 1.0.6 apply no limit to streaming requests at all.\n\nThis issue affects grpc_server: from 1.0.0 before 1.1.0."
          }
        ],
        "id": "CVE-2026-124279",
        "lastModified": "2026-11-13T17:17:20.593",
        "metrics": {
          "cvssMetricV40": [
            {
              "cvssData": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "PRESENT",
                "attackVector": "NETWORK",
                "availabilityRequirement": "NOT_DEFINED",
                "baseScore": 8.2,
                "baseSeverity": "HIGH",
                "confidentialityRequirement": "NOT_DEFINED",
                "exploitMaturity": "NOT_DEFINED",
                "integrityRequirement": "NOT_DEFINED",
                "modifiedAttackComplexity": "NOT_DEFINED",
                "modifiedAttackRequirements": "NOT_DEFINED",
                "modifiedAttackVector": "NOT_DEFINED",
                "modifiedPrivilegesRequired": "NOT_DEFINED",
                "modifiedSubAvailabilityImpact": "NOT_DEFINED",
                "modifiedSubConfidentialityImpact": "NOT_DEFINED",
                "modifiedSubIntegrityImpact": "NOT_DEFINED",
                "modifiedUserInteraction": "NOT_DEFINED",
                "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
                "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
                "modifiedVulnIntegrityImpact": "NOT_DEFINED",
                "privilegesRequired": "NONE",
                "providerUrgency": "NOT_DEFINED",
                "subAvailabilityImpact": "NONE",
                "subConfidentialityImpact": "NONE",
                "subIntegrityImpact": "NONE",
                "userInteraction": "NONE",
                "valueDensity": "NOT_DEFINED",
                "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/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",
                "version": "4.0",
                "vulnAvailabilityImpact": "HIGH",
                "vulnConfidentialityImpact": "NONE",
                "vulnIntegrityImpact": "NONE",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
              "type": "Secondary"
            }
          ]
        },
        "published": "2026-11-13T17:17:20.593",
        "references": [
          {
            "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
            "url": "https://cna.erlef.org/cves/CVE-2026-124279.html"
          },
          {
            "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
            "url": "https://github.com/elixir-grpc/grpc/commit/49e18c3ec6bb9afe2f712caad3dbab5c56a68a00"
          },
          {
            "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
            "url": "https://github.com/elixir-grpc/grpc/commit/b1e771d558941b1ed4b6de8b39f6a5375543db01"
          },
          {
            "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
            "url": "https://github.com/elixir-grpc/grpc/security/advisories/GHSA-736x-r87j-jhcm"
          },
          {
            "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
            "url": "https://osv.dev/vulnerability/EEF-CVE-2026-124279"
          }
        ],
        "sourceIdentifier": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
        "vulnStatus": "Received",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-770"
              }
            ],
            "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
            "type": "Secondary"
          }
        ]
      }
    }
  }
}

Configurations

CNA · EEF

The server must expose at least one client-streaming or bidirectional-streaming RPC method.

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted