How severe is GHSA-78hx-gp6g-7mj6?

GHSA-78hx-gp6g-7mj6 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-78hx-gp6g-7mj6?

GHSA-78hx-gp6g-7mj6 affects the following packages: github.com/golang-fips/go (Go), github.com/golang-fips/openssl/v2 (Go), github.com/microsoft/go-crypto-openssl (Go), github.com/microsoft/go-crypto-openssl/openssl (Go). Ecosystems affected: Go.

How do I fix GHSA-78hx-gp6g-7mj6?

No patched version of github.com/golang-fips/go has shipped for GHSA-78hx-gp6g-7mj6 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-78hx-gp6g-7mj6 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/golang-fips/go. 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-78hx-gp6g-7mj6 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-78hx-gp6g-7mj6?

O3 pinpoints whether GHSA-78hx-gp6g-7mj6 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-78hx-gp6g-7mj6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-78hx-gp6g-7mj6 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-78hx-gp6g-7mj6?

GHSA-78hx-gp6g-7mj6 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 72th 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-78hx-gp6g-7mj6?

GHSA-78hx-gp6g-7mj6 is classified as CWE-401 (CWE-401). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-78hx-gp6g-7mj6 published, and has it been updated?

GHSA-78hx-gp6g-7mj6 was published on March 20, 2024 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-78hx-gp6g-7mj6

HIGH

Memory leaks in code encrypting and verifying RSA payloads

Also known asCVE-2024-1394GO-2024-2660

Published

Mar 20, 2024

Updated

Feb 4, 2026

Affected

4 pkgs

Patched

2 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk72th percentile+0.15%

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.

Blast Radius

4 pkgs affected

🐹github.com/golang-fips/go🐹github.com/golang-fips/openssl/v2🐹github.com/microsoft/go-crypto-openssl🐹github.com/microsoft/go-crypto-openssl/openssl

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

Description

Using crafted public RSA keys which are not compliant with SP 800-56B can cause a small memory leak when encrypting and verifying payloads.

An attacker can leverage this flaw to gradually erode available memory to the point where the host crashes for lack of resources. Upon restart the attacker would have to begin again, but nevertheless there is the potential to deny service.

Affected Packages

4 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/golang-fips/go`	all versions	No fix
🐹Go	`github.com/golang-fips/openssl/v2`	all versions	2.0.1
🐹Go	`github.com/microsoft/go-crypto-openssl`	all versions	No fix
🐹Go	`github.com/microsoft/go-crypto-openssl/openssl`	all versions	0.2.9

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/golang-fips/go. 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
No patched version of github.com/golang-fips/go has shipped for GHSA-78hx-gp6g-7mj6 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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-78hx-gp6g-7mj6 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-78hx-gp6g-7mj6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Using crafted public RSA keys which are not compliant with SP 800-56B can cause a small memory leak when encrypting and verifying payloads. An attacker can leverage this flaw to gradually erode available memory to the point where the host crashes for lack of resources. Upon restart the attacker would have to begin again, but nevertheless there is the potential to deny service.

O3 Security · Impact-Aware SCA

Is GHSA-78hx-gp6g-7mj6 in your dependencies?

O3 detects GHSA-78hx-gp6g-7mj6 across Go 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