VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

quick-xml: vulnerability history, versions and safety

quick-xml is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 102 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 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 29 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all quick-xml vulnerabilities

Vulert verdict on quick-xml 0.42.0 i

Updated on 23 Oct 2026

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

Package health score 74/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 0.42.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 29 Jun 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 90 packages i
  • Stars 1,574 i
  • OpenSSF scorecard 4/10 i
  • Last release 2 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by crates.io, 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 quick-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.42.0 22 Aug 2026 none MIT — Details →
0.41.0 29 Jun 2026 none MIT — Details →
0.40.1 15 May 2026 U2 MIT Yes Details →
0.40.0 11 May 2026 U2 MIT Yes Details →
0.39.4 08 May 2026 U2 MIT Yes Details →
0.39.3 04 May 2026 U2 MIT Yes Details →
0.39.2 20 Feb 2026 U2 MIT Yes Details →
0.39.1 15 Feb 2026 U2 MIT Yes Details →
0.39.0 11 Jan 2026 U2 MIT Yes Details →
0.38.4 11 Nov 2025 U2 MIT Yes Details →
0.38.3 24 Aug 2025 U2 MIT Yes Details →
0.38.2 19 Aug 2025 U2 MIT Yes Details →
0.38.1 04 Aug 2025 U2 MIT Yes Details →
0.38.0 28 Jun 2025 U2 MIT Yes Details →
0.37.5 27 Apr 2025 U2 MIT Yes Details →
0.37.4 01 Apr 2025 U2 MIT Yes Details →
0.37.3 25 Mar 2025 U2 MIT Yes Details →
0.37.2 29 Dec 2024 U2 MIT Yes Details →
0.37.1 17 Nov 2024 U2 MIT Yes Details →
0.37.0 27 Oct 2024 U2 MIT Yes Details →
0.36.2 20 Sep 2024 U2 MIT Yes Details →
0.36.1 23 Jul 2024 U2 MIT Yes Details →
0.36.0 08 Jul 2024 U2 MIT Yes Details →
0.35.0 29 Jun 2024 U2 MIT Yes Details →
0.34.0 24 Jun 2024 U2 MIT Yes Details →
0.33.0 21 Jun 2024 U2 MIT Yes Details →
0.32.0 10 Jun 2024 U2 MIT Yes Details →
0.31.0 23 Oct 2023 U2 MIT Yes Details →
0.30.0 23 Jul 2023 U2 MIT Yes Details →
0.29.0 12 Jun 2023 U2 MIT Yes Details →
0.28.2 12 Apr 2023 U2 MIT Yes Details →
0.28.1 19 Mar 2023 U2 MIT Yes Details →
0.28.0 13 Mar 2023 U2 MIT Yes Details →
0.27.1 28 Dec 2022 U2 MIT Yes Details →
0.27.0 25 Dec 2022 U2 MIT Yes Details →
0.26.0 23 Oct 2022 U2 MIT Yes Details →
0.23.1 10 Sep 2022 U2 MIT Yes Details →
0.24.1 10 Sep 2022 U2 MIT Yes Details →
0.25.0 10 Sep 2022 U2 MIT Yes Details →
0.24.0 28 Aug 2022 U2 MIT Yes Details →
0.23.0 25 May 2022 U2 MIT Yes Details →
0.23.0-alpha3 21 Aug 2021 U2 MIT Yes Details →
0.23.0-alpha2 14 Aug 2021 U2 MIT Yes Details →
0.23.0-alpha1 10 Aug 2021 U2 MIT Yes Details →
0.22.0 23 Feb 2021 U2 MIT Yes Details →
0.21.0 03 Feb 2021 U2 MIT Yes Details →
0.20.0 17 Oct 2020 U2 MIT Yes Details →
0.19.0 26 Sep 2020 U2 MIT Yes Details →
0.18.1 15 Mar 2020 U2 MIT Yes Details →
0.18.0 15 Mar 2020 U2 MIT Yes Details →
0.17.2 17 Dec 2019 U2 MIT Yes Details →
0.17.1 11 Dec 2019 U2 MIT Yes Details →
0.17.0 11 Oct 2019 U2 MIT Yes Details →
0.16.1 02 Sep 2019 U2 MIT Yes Details →
0.16.0 24 Aug 2019 U2 MIT Yes Details →
0.15.0 15 Jul 2019 U2 MIT Yes Details →
0.14.0 08 Apr 2019 U2 MIT Yes Details →
0.13.3 20 Feb 2019 U2 MIT Yes Details →
0.13.2 12 Jan 2019 U2 MIT Yes Details →
0.13.1 23 Oct 2018 U2 MIT Yes Details →
0.13.0 27 Sep 2018 U2 MIT Yes Details →
0.12.4 15 Sep 2018 U2 MIT Yes Details →
0.12.3 31 Aug 2018 U2 MIT Yes Details →
0.12.2 28 Aug 2018 U2 MIT Yes Details →
0.12.1 06 Mar 2018 U2 MIT Yes Details →
0.12.0 01 Mar 2018 U2 MIT Yes Details →
0.11.0 16 Jan 2018 U2 MIT Yes Details →
0.10.1 20 Dec 2017 U2 MIT Yes Details →
0.10.0 27 Nov 2017 U2 MIT Yes Details →
0.9.4 23 Sep 2017 U2 MIT Yes Details →
0.9.3 11 Sep 2017 U2 MIT Yes Details →
0.9.2 06 Sep 2017 U2 MIT Yes Details →
0.9.1 22 Aug 2017 U2 MIT Yes Details →
0.9.0 18 Aug 2017 U2 MIT Yes Details →
0.8.1 06 Jul 2017 U2 MIT Yes Details →
0.8.0 13 Jun 2017 U2 non-standard Yes Details →
0.7.3 12 May 2017 U2 non-standard Yes Details →
0.7.2 08 May 2017 U2 non-standard Yes Details →
0.7.1 04 May 2017 U2 non-standard Yes Details →
0.7.0 22 Mar 2017 U2 non-standard Yes Details →
0.6.2 06 Mar 2017 U2 non-standard Yes Details →
0.6.1 06 Mar 2017 U2 non-standard Yes Details →
0.6.0 24 Feb 2017 U2 non-standard Yes Details →
0.5.0 16 Jan 2017 U2 non-standard Yes Details →
0.4.2 27 Nov 2016 U2 non-standard Yes Details →
0.4.1 31 Oct 2016 U2 non-standard Yes Details →
0.4.0 27 Aug 2016 U2 non-standard Yes Details →
0.3.1 04 Aug 2016 U2 non-standard Yes Details →
0.3.0 04 Aug 2016 U2 non-standard Yes Details →
0.2.4 04 Aug 2016 U2 non-standard Yes Details →
0.2.3 10 Jul 2016 U2 non-standard Yes Details →
0.2.2 03 Jul 2016 U2 non-standard Yes Details →
0.2.1 08 Jun 2016 U2 non-standard Yes Details →
0.2.0 05 May 2016 U2 non-standard Yes Details →
0.1.9 04 Apr 2016 U2 non-standard Yes Details →
0.1.8 29 Mar 2016 U2 non-standard Yes Details →
0.1.7 26 Mar 2016 U2 non-standard Yes Details →
0.1.6 25 Mar 2016 U2 non-standard Yes Details →
0.1.5 18 Mar 2016 U2 non-standard Yes Details →
0.1.4 29 Feb 2016 U2 non-standard Yes Details →
0.1.3 26 Feb 2016 U2 — Yes Details →
0.1.2 26 Feb 2016 U2 — Yes Details →
0.1.1 18 Feb 2016 U2 — Yes Details →
0.1.0 01 Feb 2016 U2 — Yes Details →

All 104 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 quick-xml

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service Vulnerability in quick-xml: Quadratic Time Complexity in Attribute Checks 7.5 high 0.41.0 29 Jun 2026
Memory Exhaustion Denial of Service in quick-xml: Unbounded Namespace Declaration Allocation 7.5 high 0.41.0 29 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: 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 quick-xml

Is quick-xml safe to use?

Vulert records 2 vulnerabilities for quick-xml in crates.io: 0 critical, 0 high, 0 medium and 0 low, plus 2 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 quick-xml's Vulert package health score?

Vulert scores quick-xml 74/100, which reads as in good shape. 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 quick-xml affected?

No. 0.42.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 quick-xml should I use?

0.42.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 quick-xml have?

2 vulnerabilities are recorded for quick-xml in the crates.io ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 2 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 quick-xml vulnerabilities disclosed?

2 vulnerabilities were recorded for quick-xml in the last 12 months, and the oldest entry in this database dates to 29 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 quick-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 quick-xml for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the quick-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.