Service interruption via unbounded JSON container loop
Published Oct 2, 2026 · Updated Oct 2, 2026
Resource exhaustion in Apache Thrift Node.js bindings before 0.25.0 allows remote attackers to interrupt RPC service via crafted JSON. TJSONProtocol uses a peer-declared container size as an unbounded loop bound instead of validating the quantity against the input. Exposure requires a service that processes untrusted RPC messages with the Node.js JSON protocol; the documented impact is service availability, not data access or modification.
Summary
What happened
Resource exhaustion in Apache Thrift Node.js bindings before 0.25.0 allows remote attackers to interrupt RPC service via crafted JSON. TJSONProtocol uses a peer-declared container size as an unbounded loop bound instead of validating the quantity against the input. Exposure requires a service that processes untrusted RPC messages with the Node.js JSON protocol; the documented impact is service availability, not data access or modification.
The record
- CVE
- CVE-2026-94645
- Published
- Oct 2, 2026
- Updated
- Oct 2, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Thrift
- Classifications
- CWE-770, CWE-1284, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 2, 2026CVE publishedPublication date reported by the CVE source.
- Oct 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.25.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started