AtomicBucket unconditionally implements Send/Sync
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (metrics-util 0.7.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
crates.io metrics-util
- Affected
- < 0.7.0
- Fixed in
- 0.7.0
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-3hxh-7jxm-59x4 lists affected ranges: crates.io metrics-util >=0 <0.7.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
In the affected versions of the crate, AtomicBucket<T unconditionally implements Send/Sync traits. Therefore, users can create a data race to the inner T: !Sync by using the AtomicBucket::datawith() API. Such data races can potentially cause memory corruption or other undefined behavior. The flaw was fixed in commit 8e6daab by adding appropriate Send/Sync bounds to the Send/Sync impl of struct Block<T (which is a data type contained inside AtomicBucket<T).
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-3hxh-7jxm-59x4
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-3hxh-7jxm-59x4 Advisory: AtomicBucket unconditionally implements Send/Sync IDs: GHSA-3hxh-7jxm-59x4 Record: https://patchnext.com/advisories/ghsa-3hxh-7jxm-59x4 (revision 1, source checked 26 Oct 2026, 15:33 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: metrics-util 0.7.0. A vendor fix does not mean a deployment is fixed. ## Affected components - crates.io metrics-util: affected < 0.7.0; fixed in 0.7.0 ## Suggested inspection (read-only) - crates.io metrics-util: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on metrics-util. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-3hxh-7jxm-59x4 (GitHub-reviewed advisory GHSA-3hxh-7jxm-59x4 lists affected ranges: crates.io metrics-util >=0 <0.7.0) Commands are suggestions: review each one before running it.
Loading voting…