Vulnerability Database · Go · Package report
github.com/gorilla/context: vulnerability history, versions and safety
github.com/gorilla/context is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/gorilla/context v1.1.2 i
Updated on 23 Oct 2026
Good news: v1.1.2, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Niche
- Community Quiet
What to do: Stay on v1.1.2 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.1.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.1.2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 431 i
- OpenSSF scorecard 3/10 i
- Last release 36 months ago i
- Licence BSD-3-Clause 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/gorilla/context, 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.
- v1.1.3-0.20231105220406-3a39c9a482f1 05 Nov 2023
- v0.0.0-20231018004633-6a490e2f9d52 18 Oct 2023
- v1.1.2 18 Oct 2023
- v1.1.2-0.20231018004633-6a490e2f9d52 18 Oct 2023
- v1.1.2-0.20230922072052-a45ea70b19f4 22 Sep 2023
- v1.1.2-0.20230731154259-1cbd4c16de64 31 Jul 2023
- v1.1.2-0.20230725003455-c492bd590c2c 25 Jul 2023
- v1.1.2-0.20230715200642-39a447022b01 15 Jul 2023
- v1.1.2-0.20230715145055-a01379df10af 15 Jul 2023
- v0.0.0-20190627024605-8559d4a6b87e 27 Jun 2019
- v1.1.2-0.20190627024605-8559d4a6b87e 27 Jun 2019
- v1.1.2-0.20190627024413-dc31bb267b79 27 Jun 2019
- v1.1.2-0.20190627024338-30a41ee8e7bf 27 Jun 2019
- v1.1.2-0.20190627023918-342e16cf46ed 27 Jun 2019
- v0.0.0-20181012153548-51ce91d2eadd 12 Oct 2018
- v1.1.2-0.20181012153548-51ce91d2eadd 12 Oct 2018
- v0.0.0-20160817184632-08b5f424b927 17 Aug 2016
- v1.1.1 17 Aug 2016
- v0.0.0-20160817152403-f81bcf7f9da1 17 Aug 2016
- v0.0.0-20160816184700-01ef6ff48fdc 16 Aug 2016
- v0.0.0-20160525203319-aed02d124ae4 25 May 2016
- v0.0.0-20160525150349-531bdb2bdc86 25 May 2016
- v0.0.0-20160422134237-a8d44e7d8e4d 22 Apr 2016
- v0.0.0-20160422132059-ffc4422d763f 22 Apr 2016
- v0.0.0-20160226214623-1ea25387ff6f 26 Feb 2016
- v0.0.0-20160226212816-b53bb424a1b6 26 Feb 2016
- v0.0.0-20150820051245-1c83b3eabd45 20 Aug 2015
- v0.0.0-20141217160251-215affda49ad 17 Dec 2014
- v0.0.0-20141126163405-50c25fb3b2b3 26 Nov 2014
- v0.0.0-20140604161150-14f550f51af5 04 Jun 2014
- v0.0.0-20140604155859-9af56363a72d 04 Jun 2014
- v0.0.0-20140522220343-1f3e8a46c5bb 22 May 2014
- v0.0.0-20140520142838-13ce75261f2d 20 May 2014
- v0.0.0-20140520030229-6e5f0a5765dc 20 May 2014
- v0.0.0-20140306180640-1be7a086a5fd 06 Mar 2014
- v0.0.0-20140306173125-116fc839c218 06 Mar 2014
- v0.0.0-20140306170551-08e2e8a9bc63 06 Mar 2014
- v0.0.0-20140306170551-3e810b0ccc2a 06 Mar 2014
- v0.0.0-20140306170551-77bafb62fdfb 06 Mar 2014
- v0.0.0-20131205071603-a08edd30ad9e 05 Dec 2013
- v0.0.0-20131130212006-257e3549c53c 30 Nov 2013
- v0.0.0-20131130002817-9192307f0e67 30 Nov 2013
- v0.0.0-20130531032101-708054d61e5a 31 May 2013
- v0.0.0-20130530143435-3968bf33e768 30 May 2013
- v0.0.0-20130409105450-a8662172a384 09 Apr 2013
- v0.0.0-20130320163141-12bc3a0632e8 20 Mar 2013
- v0.0.0-20121219211539-bbd3ed316824 19 Dec 2012
- v0.0.0-20121003044146-11ae2122d92b 03 Oct 2012
All 48 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
03 Vulnerabilities
Recorded vulnerabilities for github.com/gorilla/context
No vulnerabilities match this view.
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
Questions
About github.com/gorilla/context
Is github.com/gorilla/context safe to use?
Vulert has no vulnerabilities on record for github.com/gorilla/context in Go at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is github.com/gorilla/context's Vulert package health score?
Vulert scores github.com/gorilla/context 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).
Is the latest version of github.com/gorilla/context affected?
No. v1.1.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.
Which version of github.com/gorilla/context should I use?
v1.1.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/gorilla/context have?
0 vulnerabilities are recorded for github.com/gorilla/context in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.
How often are new github.com/gorilla/context vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/gorilla/context in the last 12 months. 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/gorilla/context 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/gorilla/context for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/gorilla/context version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.