VulertSecurity VulertSecurity

Vulnerability Database · Hex · Package report

jose: vulnerability history, versions and safety

jose is a package in the Hex ecosystem. Vulert records 1 vulnerability for it across 40 releases, first recorded in Mar 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 M1
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 jose vulnerabilities

Vulert verdict on jose 1.11.12 i

Updated on 23 Oct 2026

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

Package health score 97/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

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

  • Current release 1.11.12 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 19 Mar 2024 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Depended on by 114,155,000 packages i
  • Last release 11 months 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 jose, 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
1.11.12 20 Nov 2025 none — — Details →
1.11.11 17 Nov 2025 none — — Details →
1.11.10 17 Apr 2024 none — — Details →
1.11.9 08 Apr 2024 none — — Details →
1.11.8 07 Apr 2024 none — — Details →
1.11.7 07 Apr 2024 none — — Details →
1.11.6 18 Jul 2023 M1 — Yes Details →
1.11.5 16 Dec 2022 M1 — Yes Details →
1.11.4 16 Dec 2022 M1 — Yes Details →
1.11.2 06 Aug 2021 M1 — Yes Details →
1.11.1 23 Dec 2020 M1 — Yes Details →
1.11.0 24 Nov 2020 M1 — Yes Details →
1.10.1 08 Jan 2020 M1 — Yes Details →
1.10.0 03 Jan 2020 M1 — Yes Details →
1.9.0 31 Dec 2018 M1 — Yes Details →
1.8.4 19 May 2017 M1 — Yes Details →
1.8.3 30 Mar 2017 M1 — Yes Details →
1.8.2 15 Mar 2017 M1 — Yes Details →
1.8.1 02 Feb 2017 M1 — Yes Details →
1.8.0 09 Aug 2016 M1 — Yes Details →
1.7.9 13 Jul 2016 M1 — Yes Details →
1.7.8 08 Jul 2016 M1 — Yes Details →
1.7.7 30 Jun 2016 M1 — Yes Details →
1.7.6 29 Jun 2016 M1 — Yes Details →
1.7.5 13 May 2016 M1 — Yes Details →
1.7.4 13 May 2016 M1 — Yes Details →
1.7.3 17 Mar 2016 M1 — Yes Details →
1.7.2 16 Mar 2016 M1 — Yes Details →
1.7.1 08 Mar 2016 M1 — Yes Details →
1.7.0 02 Mar 2016 M1 — Yes Details →
1.6.1 05 Feb 2016 M1 — Yes Details →
1.6.0 21 Jan 2016 M1 — Yes Details →
1.5.2 19 Jan 2016 M1 — Yes Details →
1.5.1 17 Jan 2016 M1 — Yes Details →
1.5.0 17 Jan 2016 M1 — Yes Details →
1.4.2 30 Nov 2015 M1 — Yes Details →
1.4.1 18 Nov 2015 M1 — Yes Details →
1.4.0 18 Nov 2015 M1 — Yes Details →
1.3.0 23 Sep 2015 M1 — Yes Details →
1.2.0 14 Aug 2015 M1 — Yes Details →
1.1.3 10 Aug 2015 M1 — Yes Details →
1.1.2 10 Aug 2015 M1 — Yes Details →
1.1.1 07 Aug 2015 M1 — Yes Details →
1.1.0 06 Aug 2015 M1 — Yes Details →
1.0.1 06 Aug 2015 M1 — Yes Details →
1.0.0 06 Aug 2015 M1 — Yes 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 jose

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-50966: erlang-jose Denial of Service Vulnerability 5.3 medium 1.11.7 19 Mar 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 jose

Is jose safe to use?

Vulert records 1 vulnerabilities for jose in Hex: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is jose's Vulert package health score?

Vulert scores jose 97/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 jose affected?

No. 1.11.12, 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 jose have?

1 vulnerability is recorded for jose in the Hex ecosystem: 0 critical, 0 high, 1 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 jose vulnerabilities disclosed?

0 vulnerabilities were recorded for jose in the last 12 months, and the oldest entry in this database dates to 19 Mar 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 jose 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 jose for upcoming vulnerabilities?

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