CVE-2024-45258: req · n/a
Affects reqSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.43.4 as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.43.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade github.com/imroc/req to 3.43.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Gogithub.com/imroc/reqpkg:golang/github.com/imroc/reqOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-45258, organizations should immediately update the 'req' package to version 3.43.4 or later, where the vulnerability has been addressed. Developers should audit their codebases to identify any usage of the vulnerable 'req' package versions and replace them accordingly. Implement strict input validation and sanitization for all URLs processed by applications, especially those that interact with external or user-supplied data. Employ network-level controls such as egress filtering and web application firewalls (WAFs) to detect and block anomalous or unintended outbound HTTP requests. Conduct thorough security testing, including fuzzing and static analysis, to identify similar input validation issues in related components. Monitor application logs for unusual request patterns that may indicate exploitation attempts. Additionally, educate development teams on secure coding practices to avoid reliance on components with 'garbage in, garbage out' designs. Finally, maintain an up-to-date inventory of third-party dependencies to enable rapid response to newly disclosed vulnerabilities.
Description
The req package before 3.43.4 for Go may send an unintended request when a malformed URL is provided, because cleanHost in http.go intentionally uses a "garbage in, garbage out" design.