Out of bounds access in rgb

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2020-25016: 1.59% estimated exploitation activity in the next 30 days; percentile 75.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Affected versions of rgb crate allow viewing and modifying data of any type T wrapped in RGB<T as bytes, and do not correctly constrain RGB<T and other wrapper structures to the types for which it is safe to do so. Safety violation possible for a type wrapped in RGB<T and similar wrapper structures: If T contains padding, viewing it as bytes may lead to exposure of contents of uninitialized memory. If T contains a pointer, modifying it as bytes may lead to dereferencing of arbitrary pointers. Any safety and/or validity invariants for T may be violated. The issue was resolved by requiring all types wrapped in structures provided by RGB crate to implement an unsafe marker trait.

Published by the source

25 Aug 2021, 20:45 UTC

Last modified by the source

13 Jun 2023, 20:26 UTC

Source last checked

26 Oct 2026, 15:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g4rw-8m5q-6453

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-25016

Advisory: Out of bounds access in rgb
IDs: CVE-2020-25016, GHSA-g4rw-8m5q-6453
Record: https://patchnext.com/advisories/cve-2020-25016 (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: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: rgb 0.8.20. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io rgb: affected >= 0.5.4, < 0.8.20; fixed in 0.8.20

## Suggested inspection (read-only)
- crates.io rgb: 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 rgb.
- 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-g4rw-8m5q-6453 (GitHub-reviewed advisory GHSA-g4rw-8m5q-6453 lists affected ranges: crates.io rgb >=0.5.4 <0.8.20)

Commands are suggestions: review each one before running it.