How severe is GHSA-cj55-gc7m-wvcq?

GHSA-cj55-gc7m-wvcq has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-cj55-gc7m-wvcq?

GHSA-cj55-gc7m-wvcq affects the following packages: github.com/imroc/req/v3 (Go), github.com/imroc/req (Go), github.com/imroc/req/v2 (Go). Ecosystems affected: Go.

How do I fix GHSA-cj55-gc7m-wvcq?

Update github.com/imroc/req/v3 to 3.43.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cj55-gc7m-wvcq is resolved across your whole dependency graph.

How do I detect GHSA-cj55-gc7m-wvcq in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/imroc/req/v3. 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-cj55-gc7m-wvcq 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-cj55-gc7m-wvcq?

O3 pinpoints whether GHSA-cj55-gc7m-wvcq 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-cj55-gc7m-wvcq actively exploited in the wild?

No public exploit code has been indexed for GHSA-cj55-gc7m-wvcq 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-cj55-gc7m-wvcq?

GHSA-cj55-gc7m-wvcq has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 49th 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-cj55-gc7m-wvcq?

GHSA-cj55-gc7m-wvcq is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cj55-gc7m-wvcq published, and has it been updated?

GHSA-cj55-gc7m-wvcq was published on August 26, 2024 and was last updated on November 18, 2024. 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-cj55-gc7m-wvcq

HIGH

req may send an unintended request when a malformed URL is provided

Also known asCVE-2024-45258GO-2024-3098

Published

Aug 26, 2024

Updated

Nov 18, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk49th percentile+0.58%

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

3 pkgs affected

🐹github.com/imroc/req/v3🐹github.com/imroc/req🐹github.com/imroc/req/v2

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

The req library is a widely used HTTP library in Go. However, it does not handle malformed URLs effectively. As a result, after parsing a malformed URL, the library may send HTTP requests to unexpected destinations, potentially leading to security vulnerabilities or unintended behavior in applications relying on this library for handling HTTP requests.

Despite developers potentially utilizing the net/url library to parse malformed URLs and implement blocklists to prevent HTTP requests to listed URLs, inconsistencies exist between how the net/url and req libraries parse URLs. These discrepancies can lead to the failure of defensive strategies, resulting in potential security threats such as Server-Side Request Forgery (SSRF) and Remote Code Execution (RCE).

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/imroc/req/v3`	all versions	3.43.4
🐹Go	`github.com/imroc/req`	all versions	3.43.4
🐹Go	`github.com/imroc/req/v2`	all versions	3.43.4

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/imroc/req/v3. 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 github.com/imroc/req/v3 to 3.43.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cj55-gc7m-wvcq 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-cj55-gc7m-wvcq 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-cj55-gc7m-wvcq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The `req` library is a widely used HTTP library in Go. However, it does not handle malformed URLs effectively. As a result, after parsing a malformed URL, the library may send HTTP requests to unexpected destinations, potentially leading to security vulnerabilities or unintended behavior in applications relying on this library for handling HTTP requests. Despite developers potentially utilizing the `net/url` library to parse malformed URLs and implement blocklists to prevent HTTP requests to listed URLs, inconsistencies exist between how the `net/url` and `req` libraries parse URLs. These dis

O3 Security · Impact-Aware SCA

Is GHSA-cj55-gc7m-wvcq in your dependencies?

O3 detects GHSA-cj55-gc7m-wvcq 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