Vulnerability Database · Go · Package report

github.com/golang/glog: vulnerability history, versions and safety

github.com/golang/glog is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 54 releases, first recorded in Jan 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

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.

Vulert verdict on github.com/golang/glog v1.2.5 i

Updated on 23 Oct 2026

Action needed: v1.2.5 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

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

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v1.2.5 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 28 Jan 2025 i
  • Highest CVSS 7.1 i
  • With no published fix 0 i
  • Stars 3,599 i
  • OpenSSF scorecard 2/10 i
  • Last release 17 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/golang/glog, 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.0.0-20250429084326-2b790ef78571 29 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v1.2.5 29 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20250113095713-a0e3c40a0ed0 13 Jan 2025 M1 U1 Apache-2.0 Yes Details →
v1.2.4 13 Jan 2025 M1 U1 Apache-2.0 Yes Details →
v1.2.4-0.20250113095713-7139da234346 13 Jan 2025 M1 U1 Apache-2.0 Yes Details →
v1.2.4-0.20250113095713-a0e3c40a0ed0 13 Jan 2025 M1 U1 Apache-2.0 Yes Details →
v1.2.4-0.20250113095713-dd58629ba6ce 13 Jan 2025 M1 U1 Apache-2.0 Yes Details →
v1.2.3 05 Nov 2024 M1 U1 Apache-2.0 Yes Details →
v1.2.3-0.20241105150508-04dbec0df8d0 05 Nov 2024 M1 U1 Apache-2.0 Yes Details →
v1.2.3-0.20241104095855-459cf3b8151d 04 Nov 2024 M1 U1 Apache-2.0 Yes Details →
v1.2.2 09 Jul 2024 M1 U1 Apache-2.0 Yes Details →
v1.2.2-0.20240709130628-97303146a4ff 09 Jul 2024 M1 U1 Apache-2.0 Yes Details →
v1.2.1 04 Apr 2024 M1 U1 Apache-2.0 Yes Details →
v1.2.1-0.20240404140742-861d09475755 04 Apr 2024 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20231122112037-b256bbe5d3f8 22 Nov 2023 M1 U1 Apache-2.0 Yes Details →
v1.1.3-0.20231122112037-b256bbe5d3f8 22 Nov 2023 M1 U1 Apache-2.0 Yes Details →
v1.2.0 22 Nov 2023 M1 U1 Apache-2.0 Yes Details →
v1.1.2 09 Aug 2023 M1 U1 Apache-2.0 Yes Details →
v1.1.2-0.20230809082217-6b9d7f7df28d 09 Aug 2023 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20230322155603-03ad3c2a3f1c 22 Mar 2023 M1 U1 Apache-2.0 Yes Details →
v1.1.1 22 Mar 2023 M1 U1 Apache-2.0 Yes Details →
v1.1.1-0.20230322091445-6ce8ac99c513 22 Mar 2023 M1 U1 Apache-2.0 Yes Details →
v1.1.1-0.20230317133409-2cef961be9f6 17 Mar 2023 M1 U1 Apache-2.0 Yes Details →
v1.1.1-0.20230317133409-9c9801e69114 17 Mar 2023 M1 U1 Apache-2.0 Yes Details →
v1.1.1-0.20230317133409-c0f9e3d764d3 17 Mar 2023 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20230303143014-115d1f917240 03 Mar 2023 M1 U1 Apache-2.0 Yes Details →
v1.0.1-0.20230303143014-115d1f917240 03 Mar 2023 M1 U1 Apache-2.0 Yes Details →
v1.1.0 03 Mar 2023 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20210820115315-9ef845f417d8 20 Aug 2021 M1 U1 Apache-2.0 Yes Details →
v1.0.0 20 Aug 2021 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20210820114938-cba94dd27566 20 Aug 2021 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20210820114913-d5eac5ed654b 20 Aug 2021 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20210429001901-424d2337a529 29 Apr 2021 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20210422175149-1c8274112829 22 Apr 2021 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20160126235308-23def4e6c14b 26 Jan 2016 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20150731225221-fca8c8854093 31 Jul 2015 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20150724234432-65d674618f71 24 Jul 2015 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20141105023935-44145f04b68c 05 Nov 2014 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20141105023251-c56a6cb113f0 05 Nov 2014 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20141105021242-c741557f8f77 05 Nov 2014 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20141105020634-b83197c33c35 05 Nov 2014 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20141105020334-5066b11157b3 05 Nov 2014 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20141105015125-49850ea55f4b 05 Nov 2014 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20140115174030-d1c4472bf2ef 15 Jan 2014 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20131008212234-20cea4dfef0c 08 Oct 2013 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20130813010214-c6f9652c7179 13 Aug 2013 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20130809032924-228ba8579764 09 Aug 2013 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20130809032706-f74c4c6b9610 09 Aug 2013 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20130718072048-ab6a54c30dfa 18 Jul 2013 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20130718052832-029e58eb9ea7 18 Jul 2013 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20130717002602-496d3b747b28 17 Jul 2013 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20130717001302-2b6b49888830 17 Jul 2013 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20130716053645-3e682cc72cac 16 Jul 2013 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20130716043304-2d42ba6cf5d6 16 Jul 2013 M1 U1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/golang/glog

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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/golang/glog

Is github.com/golang/glog safe to use?

Vulert records 2 vulnerabilities for github.com/golang/glog in Go: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/golang/glog's Vulert package health score?

Vulert scores github.com/golang/glog 74/100, which reads as in good shape. 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/golang/glog affected?

Yes. v1.2.5, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/golang/glog should I use?

v1.2.5 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/golang/glog have?

2 vulnerabilities are recorded for github.com/golang/glog in the Go ecosystem: 0 critical, 0 high, 1 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/golang/glog vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/golang/glog in the last 12 months, and the oldest entry in this database dates to 28 Jan 2025. 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/golang/glog 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/golang/glog for upcoming vulnerabilities?

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