VulertSecurity VulertSecurity

Vulnerability Database · Hex · Package report

earmark: vulnerability history, versions and safety

earmark is a package in the Hex ecosystem. Vulert records 2 vulnerabilities for it across 53 releases, first recorded in Jun 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
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 17 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all earmark vulnerabilities

Vulert verdict on earmark 1.5.0-pre1 i

Updated on 22 Oct 2026

Careful: 1.5.0-pre1 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.5.0-pre1 — affected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 17 Jun 2026 i
  • Highest CVSS 4.8 i
  • With no published fix 2 i
  • Depended on by 73,813,677 packages i
  • Last release 55 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 earmark, 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.5.0-pre1 13 Mar 2022 M1 U1 — No Details →
1.5.0-pre 21 Feb 2022 M1 U1 — No Details →
1.4.49 02 Jun 2026 M1 U1 — No Details →
1.4.48 21 Jun 2025 M1 U1 — No Details →
1.4.47 12 Jul 2024 M1 U1 — No Details →
1.4.46 01 Oct 2023 M1 U1 — No Details →
1.4.45 27 Sep 2023 M1 U1 — No Details →
1.4.44 26 Sep 2023 M1 U1 — No Details →
1.4.43 20 Sep 2023 M1 U1 — No Details →
1.4.42 20 Sep 2023 M1 U1 — No Details →
1.4.41 19 Sep 2023 M1 U1 — No Details →
1.4.40 12 Sep 2023 M1 U1 — No Details →
1.4.39 14 Jul 2023 M1 U1 — No Details →
1.4.38 29 Apr 2023 M1 U1 — No Details →
1.4.37 03 Mar 2023 M1 U1 — No Details →
1.4.36 11 Feb 2023 M1 U1 — No Details →
1.4.35 27 Jan 2023 M1 U1 — No Details →
1.4.34 27 Nov 2022 M1 U1 — No Details →
1.4.33 02 Nov 2022 M1 U1 — No Details →
1.4.32 31 Oct 2022 M1 U1 — No Details →
1.4.31 20 Oct 2022 M1 U1 — No Details →
1.4.30 01 Oct 2022 M1 U1 — No Details →
1.4.29 29 Sep 2022 M1 U1 — No Details →
1.4.28 29 Sep 2022 M1 U1 — No Details →
1.4.27 11 Aug 2022 M1 U1 — No Details →
1.4.26 15 Jun 2022 M1 U1 — No Details →
1.4.25 01 May 2022 M1 U1 — No Details →
1.4.24 24 Mar 2022 M1 U1 — No Details →
1.4.23 20 Mar 2022 M1 U1 — No Details →
1.4.22 16 Mar 2022 M1 U1 — No Details →
1.4.21 14 Mar 2022 M1 U1 — No Details →
1.4.20 08 Jan 2022 M1 U1 — No Details →
1.4.19 04 Dec 2021 M1 U1 — No Details →
1.4.18 30 Oct 2021 M1 U1 — No Details →
1.4.17 27 Oct 2021 M1 U1 — No Details →
1.4.16 07 Oct 2021 M1 U1 — No Details →
1.4.16-pre2 28 Sep 2021 M1 U1 — No Details →
1.4.16-pre1 28 Sep 2021 M1 U1 — No Details →
1.4.16-pre 20 Sep 2021 M1 U1 — No Details →
1.4.15 18 Apr 2021 M1 U1 — No Details →
1.4.14 21 Feb 2021 M1 U1 — No Details →
1.4.13 03 Dec 2020 M1 U1 — No Details →
1.4.12 27 Nov 2020 M1 U1 — No Details →
1.4.10 18 Jul 2020 M1 U1 — No Details →
1.4.9 02 Jul 2020 M1 U1 — No Details →
1.4.8 01 Jul 2020 M1 U1 — No Details →
1.4.7 29 Jun 2020 M1 U1 — No Details →
1.4.6 28 Jun 2020 M1 U1 — No Details →
1.4.5 06 Jun 2020 M1 U1 — No Details →
1.4.4 01 May 2020 M1 U1 — No Details →
1.4.3 23 Nov 2019 M1 U1 — No Details →
1.4.2 14 Oct 2019 M1 U1 — No Details →
1.4.1 24 Sep 2019 M1 U1 — No Details →
1.4.0 05 Sep 2019 none — — Details →
1.3.6 30 Aug 2019 none — — Details →
1.3.5 01 Aug 2019 none — — Details →
1.3.4 29 Jul 2019 none — — Details →
1.3.3 23 Jul 2019 none — — Details →
1.3.2 23 Mar 2019 none — — Details →
1.3.1 21 Dec 2018 none — — Details →
1.3.0 15 Nov 2018 none — — Details →
1.2.6 21 Aug 2018 none — — Details →
1.2.5 02 Apr 2018 none — — Details →
1.2.4 28 Nov 2017 none — — Details →
1.2.3 26 Jul 2017 none — — Details →
1.2.2 11 May 2017 none — — Details →
1.2.1 03 May 2017 none — — Details →
1.2.0 10 Mar 2017 none — — Details →
1.1.1 03 Feb 2017 none — — Details →
1.1.0 22 Jan 2017 none — — Details →
1.0.3 02 Nov 2016 none — — Details →
1.0.2 10 Oct 2016 none — — Details →
1.0.1 06 Jul 2016 none — — Details →
1.0.0 06 Jul 2016 none — — Details →
0.2.1 15 Jan 2016 none — — Details →
0.2.0 28 Dec 2015 none — — Details →
0.1.19 27 Oct 2015 none — — Details →
0.1.18 19 Oct 2015 none — — Details →
0.1.17 18 May 2015 none — — Details →
0.1.16 08 May 2015 none — — Details →
0.1.15 25 Mar 2015 none — — Details →
0.1.14 25 Mar 2015 none — — Details →
0.1.13 31 Jan 2015 none — — Details →
0.1.12 07 Nov 2014 none — — Details →
0.1.10 13 Aug 2014 none — — Details →
0.1.9 05 Aug 2014 none — — Details →
0.1.8 02 Aug 2014 none — — Details →
0.1.7 26 Jul 2014 none — — Details →
0.1.6 25 Jul 2014 none — — Details →
0.1.5 20 Jul 2014 none — — Details →
0.1.4 16 Jul 2014 none — — Details →
0.1.3 16 Jul 2014 none — — Details →
0.1.2 16 Jul 2014 none — — Details →
0.1.1 12 Jul 2014 none — — Details →
0.1.0 09 Jul 2014 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for earmark

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-48591: Earmark Stored XSS via Unescaped HTML Attribute Values 4.8 medium No fix published 17 Jun 2026
CVE-2026-48591: Earmark Stored XSS via Unescaped HTML Attribute Values 4.8 medium No fix published 17 Jun 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 earmark

Is earmark safe to use?

Vulert records 2 vulnerabilities for earmark in Hex: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is earmark's Vulert package health score?

Vulert scores earmark 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of earmark affected?

Yes. 1.5.0-pre1, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does earmark have?

2 vulnerabilities are recorded for earmark 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 earmark vulnerabilities disclosed?

2 vulnerabilities were recorded for earmark in the last 12 months, and the oldest entry in this database dates to 17 Jun 2026. 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 earmark 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 earmark for upcoming vulnerabilities?

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