CVE-2026-48712
Received Received - Intake
Stack Overflow in protobufjs JSON Conversion

Publication date: 2026-06-22

Last updated on: 2026-06-22

Assigner: GitHub, Inc.

Description
protobufjs compiles protobuf definitions into JavaScript (JS) functions. Prior to 7.6.1 and 8.4.1, protobufjs could recurse without a depth limit while converting decoded messages to plain objects or JSON. This affected generated toObject() conversion and the custom google.protobuf.Any JSON conversion path. A crafted protobuf binary payload containing deeply nested Any values could cause the JavaScript call stack to be exhausted during conversion to JSON. This vulnerability is fixed in 7.6.1 and 8.4.1.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-22
Last Modified
2026-06-22
Generated
2026-06-23
AI Q&A
2026-06-22
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
protobufjs protobufjs to 8.4.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-674 The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-48712 is a high-severity vulnerability in the protobufjs library that affects versions up to 7.6.0 and from 8.0.0 to 8.4.0. The issue arises when protobufjs converts protobuf messages containing deeply nested google.protobuf.Any values into JSON or plain JavaScript objects. The conversion process can recurse without a depth limit, causing the JavaScript call stack to be exhausted and the process to crash.

This happens when an attacker provides a crafted protobuf binary payload with excessive nesting of Any values, triggering unbounded recursion during the conversion. The vulnerability specifically affects the toObject() conversion and the custom google.protobuf.Any JSON conversion path.

Impact Analysis

This vulnerability can cause a denial of service (DoS) by crashing the application process that uses protobufjs to convert protobuf messages to JSON or plain objects. An attacker can exploit this by sending a specially crafted protobuf payload with deeply nested Any values, exhausting the JavaScript call stack and causing the application to stop functioning.

The attack requires no privileges or user interaction and can be performed remotely over the network, making it a significant risk for applications that handle untrusted protobuf input and perform JSON conversion.

Detection Guidance

Detection of this vulnerability involves identifying if your system or application uses protobufjs versions vulnerable to CVE-2026-48712 (versions <=7.6.0 and >=8.0.0, <=8.4.0) and if it processes untrusted protobuf input containing deeply nested google.protobuf.Any values with JSON conversion.

You can check the protobufjs version used in your project by running commands like:

  • npm list protobufjs
  • yarn list protobufjs

To detect if your application is processing protobuf messages with deeply nested Any values, you may need to analyze logs or monitor for crashes related to JavaScript call stack exhaustion during JSON conversion.

There are no specific network commands provided to detect crafted protobuf payloads, but monitoring for unusual application crashes or denial of service symptoms during protobuf JSON conversion can help identify exploitation attempts.

Mitigation Strategies

Immediate mitigation steps include upgrading protobufjs to patched versions 7.6.1 or 8.4.1 where this vulnerability is fixed.

If upgrading is not immediately possible, avoid converting untrusted protobuf messages containing google.protobuf.Any values to JSON or plain objects, as the vulnerability is triggered during this conversion.

Additionally, ensure that untrusted protobuf input is validated or sanitized before processing to reduce the risk of denial of service.

Compliance Impact

The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-48712. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart