GHSA-j3w3-p6mr-3hrh json
DynFuture Drop Can Construct a Dangling Reference
published 9mo ago modified 7mo ago also RUSTSEC-2026-0079
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
DynFuture is unsound because its Drop implementation transmutes a trait-object reference into unrelated reference types, which constructs an invalid reference from trait object metadata.
This issue was reproduced against `dyn-future` 3.0.4 under Miri. The crate is unmaintained.
Is GHSA-j3w3-p6mr-3hrh in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | dyn-future | <=3.0.4 >=0.0.0-0 |
no fix listed |
Classification
- Weakness
-
- CWE-843 Access of Resource Using Incompatible Type
References
-
github.com
/rustsec/advisory-db/issues/2595
web, report
-
github.com
/xacrimon/dyn-future
package
-
rustsec.org
/advisories/RUSTSEC-2026-0079.html
web, advisory
-
crates.io
/crates/dyn-future
package
Sources
- GitHub Advisory GHSA-j3w3-p6mr-3hrh
- OSV RUSTSEC-2026-0079
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.