# CVE-2026-78334: Apache bRPC: Missing Authentication for Streaming RPC Frames


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-ghj4-cq25-h326

## What is CVE-2026-78334?

CVE-2026-78334 is a vulnerability in Apache bRPC, published on 21 Oct 2026. 

### Official description

Missing authentication in the streaming RPC path of Apache bRPC (version < 1.18.0) on all platforms allows a remote attacker to bypass server authentication and inject or deliver streaming frames, when a server is configured with an Authenticator.

Root Cause:
When authentication is configured, streaming RPC frames are consumed directly by the streaming parser (ParseStreamingMessage) and never pass through InputMessenger's authentication hook, so an unauthenticated peer can exchange frames without being authenticated. In addition, a server-accepted stream is bound lazily to the first frame that happens to carry its id, so a stream could accept a frame carrying its id from a socket other than the socket that created the stream.

Affected Scenarios:
A bRPC server configured with authentication that serves streaming RPC from an untrusted network, or a deployment where a foreign connection can impersonate a stream by id, can be made to accept unauthorized streaming frames.

How to Fix:
Upgrade bRPC to 1.18.0, which fixes this issue, or apply the patch in PR https://github.com/apache/brpc/pull/3481. 

Note:
The fix rejects streaming frames on server sockets when configured authentication has not completed, and keeps server-accepted streams bound to the socket of their creating RPC and rejects frames arriving from another socket. Authenticated streaming RPC behavior and the wire format are unchanged; only unauthenticated or foreign-socket frames are now rejected.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-78334?


## How do I fix CVE-2026-78334?

No fix has been published for CVE-2026-78334 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-78334 being exploited?

There is no known exploitation of CVE-2026-78334 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-78334 and fix it if it is affected.

What it is: CVE-2026-78334 is a vulnerability in Apache bRPC, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-78334 in the wild and no public exploit code.

Affected product: Apache bRPC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-78334/ (Markdown: https://insights.sbomify.com/CVE-2026-78334/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-78334
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-78334
- OSV: https://osv.dev/vulnerability/CVE-2026-78334

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-78334/
Summaries are generated and may contain mistakes; the official description above is the record.