Missing release of memory in sized-chunks
CVE-2020-25795GHSA-x54v-qxxr-93qc
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (sized-chunks 0.6.3), 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 sized-chunks
- Affected
- < 0.6.3
- Fixed in
- 0.6.3
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-x54v-qxxr-93qc lists affected ranges: crates.io sized-chunks >=0 <0.6.3
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
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- CVE-2020-25795: 1.73% estimated exploitation activity in the next 30 days; percentile 77.67 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Chunk: Array size is not checked when constructed with unit() and pair(). Array size is not checked when constructed with From<InlineArray<A, T. Clone and insertfrom are not panic-safe; A panicking iterator causes memory safety issues with them. InlineArray: Generates unaligned references for types with a large alignment requirement.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-x54v-qxxr-93qc
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2020-25795 Advisory: Missing release of memory in sized-chunks IDs: CVE-2020-25795, GHSA-x54v-qxxr-93qc Record: https://patchnext.com/advisories/cve-2020-25795 (revision 1, source checked 26 Oct 2026, 15:34 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: sized-chunks 0.6.3. A vendor fix does not mean a deployment is fixed. ## Affected components - crates.io sized-chunks: affected < 0.6.3; fixed in 0.6.3 ## Suggested inspection (read-only) - crates.io sized-chunks: 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 sized-chunks. - 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-x54v-qxxr-93qc (GitHub-reviewed advisory GHSA-x54v-qxxr-93qc lists affected ranges: crates.io sized-chunks >=0 <0.6.3) Commands are suggestions: review each one before running it.
Loading voting…