Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

memoffset allows reading uninitialized memory

GHSA-wfg4-322g-9vqv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (memoffset 0.6.2), 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.

Add to your agent

Affected packages

  • crates.io memoffset

    Affected
    < 0.6.2
    Fixed in
    0.6.2

Sources

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.

memoffset allows attempt of reading data from address 0 with arbitrary type. This behavior is an undefined behavior because address 0 to std::mem::sizeof<T may not have valid bit-pattern with T. Old implementation dereferences uninitialized memory obtained from std::mem::alignof. Older implementation prior to it allows using uninitialized data obtained from std::mem::uninitialized with arbitrary type then compute offset by taking the address of field-projection. This may also result in an undefined behavior for "father" that includes (directly or transitively) type that does not allow to be uninitialized. This flaw was corrected by using std::ptr::addrof in <https://github.com/Gilnaa/memoffset/pull/50.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-wfg4-322g-9vqv

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-wfg4-322g-9vqv

Advisory: memoffset allows reading uninitialized memory
IDs: GHSA-wfg4-322g-9vqv
Record: https://patchnext.com/advisories/ghsa-wfg4-322g-9vqv (revision 1, source checked 26 Oct 2026, 15:37 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: memoffset 0.6.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io memoffset: affected < 0.6.2; fixed in 0.6.2

## Suggested inspection (read-only)
- crates.io memoffset: 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 memoffset.
- 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-wfg4-322g-9vqv (GitHub-reviewed advisory GHSA-wfg4-322g-9vqv lists affected ranges: crates.io memoffset >=0 <0.6.2)

Commands are suggestions: review each one before running it.

Loading voting…