VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/coreos/go-oidc/v3: vulnerability history, versions and safety

github.com/coreos/go-oidc/v3 is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

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.

See all github.com/coreos/go-oidc/v3 vulnerabilities

Vulert verdict on github.com/coreos/go-oidc/v3 v3.21.0 i

Updated on 23 Oct 2026

Good news: v3.21.0, the version you would install today, has no known vulnerabilities.

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

What to do: Stay on v3.21.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v3.21.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v3.21.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2,497 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month 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/coreos/go-oidc/v3, 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
v3.21.0 01 Sep 2026 none Apache-2.0 — Details →
v3.20.0 08 Jul 2026 none Apache-2.0 — Details →
v3.19.1-0.20260707213132-f9049c990797 07 Jul 2026 none Apache-2.0 — Details →
v3.19.0 17 Jun 2026 none Apache-2.0 — Details →
v3.18.0 08 Apr 2026 none Apache-2.0 — Details →
v3.17.1-0.20260408031606-7271de57587b 08 Apr 2026 none Apache-2.0 — Details →
v3.17.0 21 Nov 2025 none Apache-2.0 — Details →
v3.16.0 03 Oct 2025 none Apache-2.0 — Details →
v3.15.0 30 Jul 2025 none Apache-2.0 — Details →
v3.14.1 03 Apr 2025 none Apache-2.0 — Details →
v3.14.0 03 Apr 2025 none Apache-2.0 — Details →
v3.13.0 13 Mar 2025 none Apache-2.0 — Details →
v3.12.0 04 Jan 2025 none Apache-2.0 — Details →
v3.11.0 08 Jul 2024 none Apache-2.0 — Details →
v3.10.1-0.20240708164934-308e77871b5c 08 Jul 2024 none Apache-2.0 — Details →
v3.10.1-0.20240508193912-6b94bec0d3f5 08 May 2024 none Apache-2.0 — Details →
v3.10.0 19 Mar 2024 none Apache-2.0 — Details →
v3.0.0-20231129021849-6d6be43e852d 29 Nov 2023 none Apache-2.0 — Details →
v3.9.0 29 Nov 2023 none Apache-2.0 — Details →
v3.8.0 28 Nov 2023 none Apache-2.0 — Details →
v3.0.0-20231020041522-3ebd0c9e4dcf 20 Oct 2023 none Apache-2.0 — Details →
v3.7.0 20 Oct 2023 none Apache-2.0 — Details →
v3.6.0 16 May 2023 none Apache-2.0 — Details →
v3.5.1-0.20230425000237-82f6983c39aa 25 Apr 2023 none Apache-2.0 — Details →
v3.5.1-0.20230321161233-921a42b4b63d 21 Mar 2023 none Apache-2.0 — Details →
v3.0.0-20230204015321-2936eb343ba2 04 Feb 2023 none Apache-2.0 — Details →
v3.5.1-0.20230204015321-2936eb343ba2 04 Feb 2023 none Apache-2.0 — Details →
v3.5.0 03 Jan 2023 none Apache-2.0 — Details →
v3.0.0-20221228025135-151abff909b4 28 Dec 2022 none Apache-2.0 — Details →
v3.0.0-20220909214356-fb9e00951dc7 09 Sep 2022 none Apache-2.0 — Details →
v3.4.0 09 Sep 2022 none Apache-2.0 — Details →
v3.3.0 01 Sep 2022 none Apache-2.0 — Details →
v3.2.0 11 May 2022 none Apache-2.0 — Details →
v3.1.1-0.20220324025715-2d47dd951527 24 Mar 2022 none Apache-2.0 — Details →
v3.1.1-0.20211009230704-6ce86d9e3058 09 Oct 2021 none Apache-2.0 — Details →
v3.1.0 17 Sep 2021 none Apache-2.0 — Details →
v3.0.0-20210915182415-916b64feddce 15 Sep 2021 none Apache-2.0 — Details →
v3.0.1-0.20210505164501-15b94d97d90c 05 May 2021 none Apache-2.0 — Details →
v3.0.0 11 Jan 2021 none Apache-2.0 — Details →
v3.0.0-20210111175113-fbec1bdfed4d 11 Jan 2021 none Apache-2.0 — Details →
v3.0.0-alpha.1.0.20200720190252-3bc5a7eb4df0 20 Jul 2020 none Apache-2.0 — Details →
v3.0.0-20200623032719-3344a5f3afe3 23 Jun 2020 none Apache-2.0 — Details →
v3.0.0-alpha.1 23 Jun 2020 none Apache-2.0 — Details →
v3.0.0-20200506014813-1fb281d0ee38 06 May 2020 none Apache-2.0 — Details →

All 44 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/coreos/go-oidc/v3

No vulnerability write-ups match this view

Search all 0 in the database →

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

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/coreos/go-oidc/v3

Is github.com/coreos/go-oidc/v3 safe to use?

Vulert has no vulnerabilities on record for github.com/coreos/go-oidc/v3 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/coreos/go-oidc/v3's Vulert package health score?

Vulert scores github.com/coreos/go-oidc/v3 85/100, which reads as healthy. 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/coreos/go-oidc/v3 affected?

No. v3.21.0, 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/coreos/go-oidc/v3 should I use?

v3.21.0 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/coreos/go-oidc/v3 have?

0 vulnerabilities are recorded for github.com/coreos/go-oidc/v3 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/coreos/go-oidc/v3 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/coreos/go-oidc/v3 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/coreos/go-oidc/v3 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/coreos/go-oidc/v3 for upcoming vulnerabilities?

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