Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io
Not in CISA KEV

GHSA-j3w3-p6mr-3hrh dyn-future

GHSA-j3w3-p6mr-3hrh is a security vulnerability in dyn-future. No vendor fix is recorded yet; mitigation options are listed below.

DynFuture Drop Can Construct a Dangling Reference

Also known asRUSTSEC-2026-0079
Published
Apr 4, 2026
Updated
Apr 5, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Apr 5, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🦀dyn-future

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🦀crates.iodyn-futureall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dyn-future, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of dyn-future has shipped for GHSA-j3w3-p6mr-3hrh yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-j3w3-p6mr-3hrh can be triaged on real exposure rather than presence alone.

Tailored to GHSA-j3w3-p6mr-3hrh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-j3w3-p6mr-3hrh in your dependencies?

O3 Security finds GHSA-j3w3-p6mr-3hrh across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-j3w3-p6mr-3hrh: dyn-future | O3 Security