dbcve.org
BrpcApplication · Apache

CVE-2025-59789

HIGH · 7.5 CVSS v3.1 Published 2025-12-01
Fix available
A fix is available. Upgrade to 1.15.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Uncontrolled recursion in the json2pb component in Apache bRPC (version < 1.15.0) on all platforms allows remote attackers to make the server crash via sending deep recursive json data. Root Cause: The bRPC json2pb component uses rapidjson to parse json data from the network. The rapidjson parser uses a recursive parsing method by default. If the input json has a large depth of recursive structure, the parser function may run into stack overflow. Affected Scenarios: Use bRPC server with protobuf message to serve http+json requests from untrusted network. Or directly use JsonToProtoMessage to convert json from untrusted input. How to Fix: (Choose one of the following options)  1. Upgrade bRPC to version 1.15.0, which fixes this issue. 2. Apply this patch: https://github.com/apache/brpc/pull/3099 Note: No matter which option you choose, you should know that the fix introduces a recursion depth limit with default value 100. It affects these functions:  ProtoMessageToJson, ProtoMessageToProtoJson, JsonToProtoMessage, and ProtoJsonToProtoMessage. If your requests contain json or protobuf messages that have a depth exceeding the limit, the request will be failed after applying the fix. You can modify the gflag json2pb_max_recursion_depth to change the limit.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BrpcApplication
Affected:< 1.15.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.15.0 or later
Fixed in 1.15.0
Vendor patch lists.apache.org →
Recommended fix High confidence

1.15.0

  1. 1. Identify all services and systems running bRPC versions earlier than 1.15.0 using your deployment inventory or by checking the compiled bRPC library version.
  2. 2. Stop the bRPC services or set up a maintenance window to ensure no active connections during the upgrade.
  3. 3. Upgrade bRPC to version 1.15.0 or later. If using a package manager (e.g., apt, yum, or a language-specific package manager), use the appropriate command to install the new version. For source builds, clone the repository and checkout tag 1.15.0 or a later release, then rebuild and reinstall.
  4. 4. In a staging or testing environment, verify that legitimate JSON/protobuf requests work correctly. Pay special attention to messages with structural depth (nested objects/arrays) approaching 100 levels.
  5. 5. If your application requires handling JSON with depth greater than the default limit of 100, configure the gflag json2pb_max_recursion_depth to a higher value before deploying to production. Example: --json2pb_max_recursion_depth=200
  6. 6. Deploy the upgraded bRPC to production services.
  7. 7. Monitor logs for failures containing messages related to recursion depth limits. If failures occur, adjust json2pb_max_recursion_depth accordingly or refactor the JSON structure to reduce depth.
Caveat The default recursion depth limit of 100 may cause request failures for deep JSON structures; adjust json2pb_max_recursion_depth gflag if needed

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59789 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59789 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data