VulertSecurity VulertSecurity

Vulnerability Database · Hex · Package report

oidcc: vulnerability history, versions and safety

oidcc is a package in the Hex ecosystem. Vulert records 2 vulnerabilities for it across 23 releases, from Apr 2024 to Aug 2026. 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
1 in the last 12 months

Most recent disclosure 30 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all oidcc vulnerabilities

Vulert verdict on oidcc 3.9.0 i

Updated on 23 Oct 2026

Good news: 3.9.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 93/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

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

  • Current release 3.9.0 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 1 in the last year i
  • Latest disclosure 30 Aug 2026 i
  • Highest CVSS 7.6 i
  • With no published fix 0 i
  • Depended on by 932,692 packages i
  • Last release 1 month ago i

Version list, release dates, licence and dependants published by hex.pm, 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 oidcc, 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
3.9.0 30 Aug 2026 none — — Details →
3.8.0 29 Jul 2026 U1 — Yes Details →
3.8.0-beta.1 29 Jul 2026 U1 — Yes Details →
3.7.2 14 Apr 2026 U1 — Yes Details →
3.7.1 09 Apr 2026 U1 — Yes Details →
3.7.0 11 Dec 2025 U1 — Yes Details →
3.6.0 15 Sep 2025 U1 — Yes Details →
3.5.2 05 May 2025 U1 — Yes Details →
3.5.1 07 Apr 2025 U1 — Yes Details →
3.5.0 04 Apr 2025 U1 — Yes Details →
3.4.0 02 Apr 2025 U1 — Yes Details →
3.3.0 21 Feb 2025 U1 — Yes Details →
3.2.6 14 Nov 2024 U1 — Yes Details →
3.2.5 04 Nov 2024 U1 — Yes Details →
3.2.4 10 Sep 2024 U1 — Yes Details →
3.2.3 03 Sep 2024 U1 — Yes Details →
3.2.2 24 Aug 2024 U1 — Yes Details →
3.2.1 12 Aug 2024 U1 — Yes Details →
3.2.0 30 Apr 2024 U1 — Yes Details →
3.2.0-beta.3 03 Apr 2024 U1 — Yes Details →
3.2.0-beta.2 25 Mar 2024 U1 — Yes Details →
3.2.0-beta.1 21 Feb 2024 U1 — Yes Details →
3.1.2 03 Apr 2024 none — — Details →
3.1.2-beta.1 13 Dec 2023 none — — Details →
3.1.1 07 Dec 2023 none — — Details →
3.1.0 29 Nov 2023 none — — Details →
3.1.0-beta.2 21 Nov 2023 none — — Details →
3.1.0-beta.1 22 Oct 2023 none — — Details →
3.0.2 03 Apr 2024 none — — Details →
3.0.1 17 Oct 2023 M1 — Yes Details →
3.0.0 29 Sep 2023 M1 — Yes Details →
3.0.0-rc.6 26 Sep 2023 none — — Details →
3.0.0-rc.5 25 Sep 2023 none — — Details →
3.0.0-rc.4 22 Sep 2023 none — — Details →
3.0.0-rc.3 20 Sep 2023 none — — Details →
3.0.0-rc.2 19 Sep 2023 none — — Details →
3.0.0-rc.1 19 Sep 2023 none — — Details →
3.0.0-alpha.5 18 Sep 2023 none — — Details →
3.0.0-alpha.4 14 Sep 2023 none — — Details →
3.0.0-alpha.3 13 Sep 2023 none — — Details →
3.0.0-alpha.2 11 Sep 2023 none — — Details →
3.0.0-alpha.1 11 Sep 2023 none — — Details →
2.0.0-alpha.2 23 Nov 2021 none — — Details →
2.0.0-alpha.1 01 Oct 2021 none — — Details →
1.8.1 24 Jun 2021 none — — Details →
1.8.0 15 Aug 2018 none — — Details →
1.7.0 19 Dec 2017 none — — Details →
1.6.0 19 Dec 2017 none — — Details →
1.5.1 13 Sep 2017 none — — Details →
1.5.0 26 Jun 2017 none — — Details →
1.4.0 01 Jun 2017 none — — Details →
1.3.0 30 Mar 2017 none — — Details →
1.2.1 28 Mar 2017 none — — Details →
1.2.0 24 Mar 2017 none — — Details →
1.1.0 23 Mar 2017 none — — Details →
1.0.1 30 Jan 2017 none — — Details →
1.0.0 27 Jan 2017 none — — Details →

All 57 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
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for oidcc

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-75759: oidcc Package Vulnerability - Improper Signature Verification in Encrypted ID Tokens 7.6 high 3.9.0 30 Aug 2026
OpenID Connect client Atom Exhaustion in provider configuration worker ets table location in oidcc 5.3 medium 3.0.2 03 Apr 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 oidcc

Is oidcc safe to use?

Vulert records 2 vulnerabilities for oidcc in Hex: 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 oidcc's Vulert package health score?

Vulert scores oidcc 93/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 oidcc affected?

No. 3.9.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.

How many vulnerabilities does oidcc have?

2 vulnerabilities are recorded for oidcc in the Hex 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 oidcc vulnerabilities disclosed?

1 vulnerability was recorded for oidcc in the last 12 months, and the oldest entry in this database dates to 03 Apr 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 oidcc 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 oidcc for upcoming vulnerabilities?

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