{"id":8413,"date":"2026-06-08T12:22:33","date_gmt":"2026-06-08T12:22:33","guid":{"rendered":"https:\/\/cybersecurityinfocus.com\/?p=8413"},"modified":"2026-06-08T12:22:33","modified_gmt":"2026-06-08T12:22:33","slug":"protocol-buffers-schemas-expose-remote-code-execution-risk","status":"publish","type":"post","link":"https:\/\/cybersecurityinfocus.com\/?p=8413","title":{"rendered":"Protocol Buffers schemas expose remote code execution risk"},"content":{"rendered":"
\n
\n
\n
\n
<\/div>\n

A widely used JavaScript implementation of Google\u2019s Protocol Buffers<\/a> format is placing too much trust in untrusted data, exposing affected applications to remote code execution and other attacks.<\/p>\n

Researchers at Cyera have disclosed six vulnerabilities affecting \u201cprotobuf.js<\/a>,\u201d all stemming from the library\u2019s handling of schema and metadata. Attackers could exploit an input validation oversight to insert malicious data and influence an application\u2019s behavior.<\/p>\n

Protocol Buffers is a technology for packaging data in a compact, structured format to streamline the exchange of information between different applications. The protobuf.js library reportedly receives more than 50 million weekly downloads. It is commonly pulled into applications indirectly through dependencies such as gRPC tooling, Google Cloud libraries, and other frameworks, making it difficult for organizations to track.<\/p>\n

Researchers disclosed six CVE<\/a>s covering remote code execution, denial-of-service (DoS) conditions, prototype pollution, prototype injection, and code-generation issues.<\/p>\n

\u201cWhile exploitation of these vulnerabilities generally requires specific conditions, those conditions are increasingly common in data and AI ecosystems that routinely exchange data, schemas, and configuration files across services, repositories, cloud platforms, and third-party integrations,\u201d Cyera researchers Assaf Morag and Vladimir Tokarev said in a blog post<\/a>.<\/p>\n

Patches are available for both protobuf.js and protonufjs-cli, the project\u2019s command-line code generation tools.<\/p>\n

Metadata capable of writing code<\/h2>\n

The most significant of the bugs is a code-generation flaw tracked as CVE-2026-44291<\/a>.<\/p>\n

According to Cyera, protobuf.js dynamically generates encoder and decoder functions and compiles them using JavaScript\u2019s Function () constructor. Under specific conditions, an attacker can manipulate schema-derived information so that data intended to describe a message instead becomes executable code.<\/p>\n

The researchers demonstrated an attack chain in which prototype pollution is used to trick protobuf.js into accepting attacker-controlled values as legitimate protobuf types. Those values are then incorporated into the generated code and executed within the Node.js process.<\/p>\n

The impact extends beyond runtime applications. A separate code-injection issue, tracked as CVE-2026-44295<\/a>, affects the pbjs command-line tool, where crafted schema names can be embedded into generated JavaScript files and executed when those files are later imported.<\/p>\n

While successful exploitation requires specific preconditions, such as the ability to influence protobuf schemas or descriptors, researchers noted that modern software increasingly exchanges schemas, descriptors, and configuration files across repositories, cloud environments, APIs, and third-party integrations, making those assumptions less restrictive than they once were.<\/p>\n

The remaining vulnerabilities are less severe. Researchers identified a prototype injection (CVE-2026-44292<\/a>) flaw that can alter application behavior by tampering with inherited object properties, as well as denial-of-services (DoS) bugs (CVE-2026-44289<\/a>, CVE-2026-44290<\/a>, and CVE-2026-44294<\/a>) that can crash or exhaust application resources using maliciously crafted inputs.<\/p>\n

Patching advised as supply chain risk looms<\/h2>\n

The researchers noted that protobuf.js is often consumed as a transitive dependency, meaning organizations may be exposed without realizing the library is present in their software stack. As schemas move through automated development pipelines and software supply chains<\/a>, components traditionally viewed as passive data can become a pathway for attacks.<\/p>\n

\u201cDevelopment teams routinely accept code contributions, integrate third-party components, and automatically process files through CI\/CD pipelines,\u201d they explained. \u201cWe found that under certain conditions, a malicious protobuf schema could be introduced into this workflow and ultimately executed within trusted build environments.\u201d<\/p>\n

A compromise at this stage could have downstream impacts on products, customers, and business operations, they added.<\/p>\n

The vulnerabilities affect protobuf.js versions 7.5.5 and earlier, along with versions 8.0.0 and 8.0.1, as well as vulnerable releases of protobuf.js-cli. Patches are available in protobuf.js 7.5.6 and 8.0.2, while protobuf.js-cli users are advised to upgrade to versions 1.2.1 or 2.0.2.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"

A widely used JavaScript implementation of Google\u2019s Protocol Buffers format is placing too much trust in untrusted data, exposing affected applications to remote code execution and other attacks. Researchers at Cyera have disclosed six vulnerabilities affecting \u201cprotobuf.js,\u201d all stemming from the library\u2019s handling of schema and metadata. Attackers could exploit an input validation oversight to […]<\/p>\n","protected":false},"author":0,"featured_media":8414,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-8413","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-education"],"_links":{"self":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/posts\/8413"}],"collection":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=8413"}],"version-history":[{"count":0,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/posts\/8413\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=\/wp\/v2\/media\/8414"}],"wp:attachment":[{"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=8413"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=8413"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cybersecurityinfocus.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=8413"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}