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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

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 69th 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

Multiple memory safety issues in actix-webGHSA-w65j-g6c7-g3m4

GHSA-w65j-g6c7-g3m4 is a Out-of-bounds Write vulnerability in actix-web. A fix is available for actix-web — see the affected versions and patch details below.

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 Oct 11, 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 CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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`cargo update -p actix-web --precise 0.7.19`

Affected Products

1 product · 1 configurations

Application

actix-webactix

< 0.7.15

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

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?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works