dbcve.org
BrpcApplication · Apache

CVE-2025-60021

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-16
Fix available
A fix is available. Upgrade to 1.15.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Remote command injection vulnerability in heap profiler builtin service in Apache bRPC ((all versions < 1.15.0)) on all platforms allows attacker to inject remote command. Root Cause: The bRPC heap profiler built-in service (/pprof/heap) does not validate the user-provided extra_options parameter and executes it as a command-line argument. Attackers can execute remote commands using the extra_options parameter.. Affected scenarios: Use the built-in bRPC heap profiler service to perform jemalloc memory profiling. How to Fix: we provide two methods, you can choose one of them: 1. Upgrade bRPC to version 1.15.0. 2. Apply this patch ( https://github.com/apache/brpc/pull/3101 ) manually.

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 · high confidence

Apache bRPC heap profiler built-in service (/pprof/heap) does not validate the extra_options parameter, allowing attackers to inject arbitrary command-line arguments and achieve remote command execution with CVSS 9.8 critical severity.

MitigationUpgrade bRPC to version 1.15.0 or apply the upstream patch from PR #3101 to add input validation to the extra_options parameter in the heap profiler service.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.11.0, < 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
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Apache bRPC version
    Locate the bRPC library or server binary and retrieve its version information (check binary metadata, library version, or build configuration)
    Affected if The version is >= 1.11.0 and < 1.15.0
  2. Verify the heap profiler service endpoint exists
    Inspect the bRPC server configuration or confirm the /pprof/heap endpoint is registered and available on the running service
    Affected if The /pprof/heap endpoint is enabled and accessible
  3. Confirm network accessibility of the profiler endpoint
    Determine whether the bRPC server listening port is exposed to untrusted networks or the internet (check firewall rules, bind addresses, and access controls)
    Affected if The /pprof/heap service is reachable without proper authentication from untrusted sources

You are affected if your installed bRPC version falls within 1.11.0 to less than 1.15.0 AND the heap profiler service (/pprof/heap) is enabled and accessible to potentially malicious network callers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Interim mitigation

Upgrade bRPC to version 1.15.0 or apply the upstream patch from PR #3101 to add input validation to the extra_options parameter in the heap profiler service.

Recommended fix High confidence

1.15.0

  1. 1. Identify current bRPC version in use by checking thebrpc library version in your project dependencies or build configuration.
  2. 2. Confirm the deployed version is within the vulnerable range (>= 1.11.0 and < 1.15.0).
  3. 3. Download bRPC version 1.15.0 from the official Apache bRPC repository (https://github.com/apache/brpc).
  4. 4. Update your project's dependency configuration to specify bRPC version 1.15.0.
  5. 5. Rebuild your application with the upgraded bRPC library.
  6. 6. Redeploy the updated application.
  7. 7. Verify that the /pprof/heap service now properly validates the extra_options parameter and no longer allows command injection.
Caveat Review release notes for 1.15.0 to check for any API or behavioral changes that may affect your application; minor version upgrades typically have minimal breaking changes.

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

Fix this in Brpc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,736.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60021 — 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-60021 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