VulertSecurity VulertSecurity

Vulnerability Database · Hex · Package report

sweet_xml: vulnerability history, versions and safety

sweet_xml is a package in the Hex ecosystem. Vulert records 1 vulnerability for it across 15 releases, first recorded in Apr 2022. 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 H1
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 sweet_xml vulnerabilities

Vulert verdict on sweet_xml 0.7.5 i

Updated on 23 Oct 2026

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

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

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

  • Current release 0.7.5 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 12 Apr 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 72,851,308 packages i
  • Last release 21 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 sweet_xml, 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
0.7.5 07 Jan 2025 none — — Details →
0.7.4 31 Aug 2023 none — — Details →
0.7.3 11 Apr 2022 none — — Details →
0.7.2 25 Nov 2021 none — — Details →
0.7.1 25 Aug 2021 none — — Details →
0.7.0 02 Jul 2021 none — — Details →
0.6.6 23 Feb 2019 H1 — Yes Details →
0.6.5 08 Feb 2017 H1 — Yes Details →
0.6.4 17 Jan 2017 H1 — Yes Details →
0.6.3 14 Dec 2016 H1 — Yes Details →
0.6.2 12 Oct 2016 H1 — Yes Details →
0.6.1 10 Feb 2016 H1 — Yes Details →
0.6.0 09 Feb 2016 H1 — Yes Details →
0.5.1 08 Feb 2016 H1 — Yes Details →
0.5.0 28 Oct 2015 H1 — Yes Details →
0.4.0 11 Sep 2015 H1 — Yes Details →
0.3.0 10 Aug 2015 H1 — Yes Details →
0.2.1 12 Apr 2015 H1 — Yes Details →
0.2.0 11 Apr 2015 H1 — Yes Details →
0.1.1 09 Sep 2014 H1 — Yes Details →
0.1.0 24 Jul 2014 H1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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 sweet_xml

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-15160: XML Bomb Attack in SweetXml Package 7.5 high 0.7.0 12 Apr 2022

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 sweet_xml

Is sweet_xml safe to use?

Vulert records 1 vulnerabilities for sweet_xml in Hex: 0 critical, 1 high, 0 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 sweet_xml's Vulert package health score?

Vulert scores sweet_xml 90/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 sweet_xml affected?

No. 0.7.5, 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 sweet_xml have?

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

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

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