Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-qwgh-2vcv-g2f7

block_buffer: panic corrupts inline buffer position

CVSS 4.0, no score published

Published by the GitHub Advisory Database at 19 Aug 2026, 19:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
block_buffercrates.io>=0.11.0, <0.12.10.12.1
Identifiers
GHSA-qwgh-2vcv-g2f7
Weakness (CWE)
CWE-119
Tags
Published
19 Aug 2026
Updated
30 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The block_buffer crate, versions 0.11.0 up to but not including 0.12.1, can have the cursor position of EagerBuffer or ReadBuffer left corrupted after a caught panic, which can lead to out-of-bounds reads and writes. Exploitation requires that the surrounding code catches a panic and keeps running, and that an attacker can trigger a panic; the source does not establish how feasible that is. Upgrade to block_buffer 0.12.1, which is the fixed version.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
Not published None 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.