VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/imroc/req: vulnerability history, versions and safety

github.com/imroc/req is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 46 releases, first recorded in Sep 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/imroc/req vulnerabilities

Vulert verdict on github.com/imroc/req v0.3.2 i

Updated on 23 Oct 2026

Careful: v0.3.2 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v0.3.2 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 13 Sep 2024 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Stars 4,867 i
  • OpenSSF scorecard 4/10 i
  • Last release 59 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/imroc/req, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.3.3-0.20220121103501-a5e3331ea7d8 21 Jan 2022 U1 Apache-2.0 No Details →
v0.3.3-0.20220121102945-f7ae3a6a8afc 21 Jan 2022 U1 Apache-2.0 No Details →
v0.3.2 10 Nov 2021 U1 Apache-2.0 No Details →
v0.3.1 27 Oct 2021 U1 Apache-2.0 No Details →
v0.3.1-0.20210929065319-1e6ea56be5a9 29 Sep 2021 U1 Apache-2.0 No Details →
v0.3.1-0.20200925013843-900b1a725aa8 25 Sep 2020 U1 Apache-2.0 No Details →
v0.0.0-20200126073949-d679d25f09a2 26 Jan 2020 U1 Apache-2.0 No Details →
v0.3.0 26 Jan 2020 U1 Apache-2.0 No Details →
v0.2.4-0.20200125155951-472d7da5e8bd 25 Jan 2020 U1 Apache-2.0 No Details →
v0.0.0-20190919054932-6799276e1f61 19 Sep 2019 U1 Apache-2.0 No Details →
v0.2.4-0.20190919054932-6799276e1f61 19 Sep 2019 U1 Apache-2.0 No Details →
v0.2.4-0.20190919041951-def36f2fd4ef 19 Sep 2019 U1 Apache-2.0 No Details →
v0.2.4-0.20190826080301-9120b6805e52 26 Aug 2019 U1 Apache-2.0 No Details →
v0.2.4-0.20190825173021-ba3ab2595763 25 Aug 2019 U1 Apache-2.0 No Details →
v0.0.0-20190815013240-fc8e4797bca7 15 Aug 2019 U1 Apache-2.0 No Details →
v0.2.4-0.20190815013240-fc8e4797bca7 15 Aug 2019 U1 Apache-2.0 No Details →
v0.0.0-20190620021506-b713f8758bce 20 Jun 2019 U1 Apache-2.0 No Details →
v0.2.4-0.20190620021506-b713f8758bce 20 Jun 2019 U1 Apache-2.0 No Details →
v0.0.0-20190620021422-1c31a6577f8d 20 Jun 2019 U1 Apache-2.0 No Details →
v0.2.4 20 Jun 2019 U1 Apache-2.0 No Details →
v0.0.0-20190517095131-ac2d62cf8536 17 May 2019 U1 Apache-2.0 No Details →
v0.2.4-0.20190517095131-ac2d62cf8536 17 May 2019 U1 Apache-2.0 No Details →
v0.0.0-20181125100431-b355b6f6842f 25 Nov 2018 U1 Apache-2.0 No Details →
v0.2.3 25 Nov 2018 U1 Apache-2.0 No Details →
v0.2.2 23 Nov 2018 U1 Apache-2.0 No Details →
v0.0.0-20181031143727-70c6d4ee7c8c 31 Oct 2018 U1 Apache-2.0 No Details →
v0.2.2-0.20181031143727-70c6d4ee7c8c 31 Oct 2018 U1 Apache-2.0 No Details →
v0.0.0-20180925131533-bc0679ab8b32 25 Sep 2018 U1 Apache-2.0 No Details →
v0.2.1 25 Sep 2018 U1 Apache-2.0 No Details →
v0.2.0 24 Sep 2018 U1 Apache-2.0 No Details →
v0.0.0-20180207070313-b02e5d142b50 07 Feb 2018 U1 Apache-2.0 No Details →
v0.1.10-0.20180207070313-b02e5d142b50 07 Feb 2018 U1 Apache-2.0 No Details →
v0.0.0-20180206115922-2a9647f3b8f6 06 Feb 2018 U1 Apache-2.0 No Details →
v0.1.9 06 Feb 2018 U1 Apache-2.0 No Details →
v0.1.8 06 Dec 2017 U1 Apache-2.0 No Details →
v0.1.7 22 Oct 2017 U1 Apache-2.0 No Details →
v0.1.6 15 Oct 2017 U1 Apache-2.0 No Details →
v0.0.0-20170612011141-127e8b679610 12 Jun 2017 U1 Apache-2.0 No Details →
v0.1.6-0.20170612011141-127e8b679610 12 Jun 2017 U1 Apache-2.0 No Details →
v0.1.5 07 Jun 2017 U1 Apache-2.0 No Details →
v0.1.4 06 Jun 2017 U1 Apache-2.0 No Details →
v0.1.3 04 Jun 2017 U1 Apache-2.0 No Details →
v0.1.1 03 Jun 2017 U1 Apache-2.0 No Details →
v0.1.0 02 Jun 2017 U1 Apache-2.0 No Details →
v0.0.0-20170408092005-7f11e9fd61e3 08 Apr 2017 U1 Apache-2.0 No Details →
v0.0.0-20170327085055-8d6ba265220a 27 Mar 2017 U1 Apache-2.0 No Details →

All 46 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/imroc/req

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-45258: Vulnerability in github.com/imroc/req N/A unrated No fix published 13 Sep 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/imroc/req

Is github.com/imroc/req safe to use?

Vulert records 1 vulnerabilities for github.com/imroc/req in Go: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is github.com/imroc/req's Vulert package health score?

Vulert scores github.com/imroc/req 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/imroc/req affected?

Yes. v0.3.2, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/imroc/req should I use?

v0.3.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/imroc/req have?

1 vulnerability is recorded for github.com/imroc/req in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/imroc/req vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/imroc/req in the last 12 months, and the oldest entry in this database dates to 13 Sep 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/imroc/req are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/imroc/req for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/imroc/req version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.