RUSTSEC-2026-0348: Brotli certificate decompression can allocate up to 1 GiB before authentication
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 50/100
Research direction
The payload names the rustls dependency at 0.23.45 with a patched version of at least 0.23.46, but not where it is declared. Start by searching Cargo.toml and Cargo.lock for rustls, and check whether the brotli feature is enabled anywhere. Done when the lock resolves to a patched rustls and the project builds and its tests pass; cargo audit should no longer report RUSTSEC-2026-0348.
Written by the indexing model from the issue text.
Description
Brotli certificate decompression can allocate up to 1 GiB before authentication
| Details | |
|---|---|
| Package | rustls |
| Version | 0.23.45 |
| URL | https://github.com/rustls/rustls/pull/3297 |
| Date | 2026-10-14 |
| Patched versions | >=0.23.46 |
| Unaffected versions | <0.23.9 |
The built-in Brotli certificate decompressor (enabled by the non-default
brotli crate feature) bounded the size of the decompressed output, but
accepted a peer-selected history window. Brotli's large-window extension was
enabled, so a five-byte header could cause an allocation of 1 GiB. A peer can
abort a process whose allocator cannot satisfy that request.
No trusted certificate is required by the attacker. Affected configurations are:
- clients that enable the
brotlifeature and connect to a malicious server, and - servers that enable the
brotlifeature and request client certificates.
Applications that do not enable the brotli feature are not affected.
See advisory page for additional details.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stackabletech/stackable-odbc-trino
-
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in stackabletech/stackable-odbc-trino
Similar issues
-
area: compat area: parsing bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
reubeno/brush#1526 · 1 comment ·
Maintainers usually reply within 1 day
-
OFN writer emits `DocIRI` as a bare IRI, which becomes a version IRI or a parse error on re-readOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
phillord/horned-owl#338 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stackabletech/operator-rs#1301 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
jmcnamara/rust_xlsxwriter#205 · 4 comments ·