How severe is GHSA-w65j-g6c7-g3m4?

No CVSS score has been assigned to GHSA-w65j-g6c7-g3m4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w65j-g6c7-g3m4?

GHSA-w65j-g6c7-g3m4 affects the following packages: actix-web (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-w65j-g6c7-g3m4?

Update actix-web to 0.7.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w65j-g6c7-g3m4 is resolved across your whole dependency graph.

How do I detect GHSA-w65j-g6c7-g3m4 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for actix-web. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-w65j-g6c7-g3m4 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-w65j-g6c7-g3m4?

O3 pinpoints whether GHSA-w65j-g6c7-g3m4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-w65j-g6c7-g3m4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-w65j-g6c7-g3m4 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-w65j-g6c7-g3m4?

GHSA-w65j-g6c7-g3m4 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 68th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-w65j-g6c7-g3m4?

GHSA-w65j-g6c7-g3m4 is classified as Out-of-bounds Write (CWE-787). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w65j-g6c7-g3m4 published, and has it been updated?

GHSA-w65j-g6c7-g3m4 was published on August 25, 2021 and was last updated on June 9, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-w65j-g6c7-g3m4

GHSA-w65j-g6c7-g3m4 is a Out-of-bounds Write vulnerability in actix-web. O3 Security confirms whether GHSA-w65j-g6c7-g3m4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Multiple memory safety issues in actix-web

Also known asCVE-2018-25024 CVE-2018-25025 CVE-2018-25026 GHSA-7x36-h62w-vw65 GHSA-9qj6-4rfq-vm84 GHSA-fgfm-hqjw-3265

Published

Aug 25, 2021

Updated

Jun 9, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🦀actix-web

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

Affected versions contain multiple memory safety issues, such as:

Unsoundly coercing immutable references to mutable references
Unsoundly extending lifetimes of strings
Adding the Send marker trait to objects that cannot be safely sent between threads

This may result in a variety of memory corruption scenarios, most likely use-after-free.

A signficant refactoring effort has been conducted to resolve these issues.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`actix-web`	all versions	0.7.19

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for actix-web. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update actix-web to 0.7.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w65j-g6c7-g3m4 is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 pinpoints whether GHSA-w65j-g6c7-g3m4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-w65j-g6c7-g3m4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions contain multiple memory safety issues, such as: - Unsoundly coercing immutable references to mutable references - Unsoundly extending lifetimes of strings - Adding the `Send` marker trait to objects that cannot be safely sent between threads This may result in a variety of memory corruption scenarios, most likely use-after-free. A signficant refactoring effort has been conducted to resolve these issues.

O3 Security · Impact-Aware SCA

Is GHSA-w65j-g6c7-g3m4 in your dependencies?

O3 detects GHSA-w65j-g6c7-g3m4 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works