VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

signxml: vulnerability history, versions and safety

signxml is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 77 releases, from Jun 2025 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M2 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 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all signxml vulnerabilities

Vulert verdict on signxml 5.2.0 i

Updated on 23 Oct 2026

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

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 5.2.0 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 2 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 6.9 i
  • With no published fix 0 i
  • Depended on by 59 packages i
  • Stars 155 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, 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 signxml, 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
5.2.0 18 Oct 2026 none non-standard — Details →
5.1.0 05 Jul 2026 none non-standard — Details →
5.0.1 23 Jun 2026 none non-standard — Details →
5.0.0 21 Jun 2026 none non-standard — Details →
4.5.1 13 Jun 2026 none non-standard — Details →
4.4.0 01 Mar 2026 none non-standard — Details →
4.3.1 18 Feb 2026 none non-standard — Details →
4.3.0 14 Feb 2026 none non-standard — Details →
4.2.2 21 Jan 2026 none non-standard — Details →
4.2.1 19 Jan 2026 none non-standard — Details →
4.2.0 20 Aug 2025 none non-standard — Details →
4.1.0 28 Jun 2025 none non-standard — Details →
4.0.5 02 Jun 2025 none non-standard — Details →
4.0.4 01 Jun 2025 none non-standard — Details →
4.0.3 24 Nov 2024 M2 U2 non-standard Yes Details →
4.0.2 11 Sep 2024 M2 U2 non-standard Yes Details →
4.0.1 30 Aug 2024 M2 U2 non-standard Yes Details →
4.0.0 22 Aug 2024 M2 U2 non-standard Yes Details →
3.2.2 29 Jan 2024 M2 U2 non-standard Yes Details →
3.2.1 06 Aug 2023 M2 U2 non-standard Yes Details →
3.2.0 13 Apr 2023 M2 U2 non-standard Yes Details →
3.1.1 08 Apr 2023 M2 U2 non-standard Yes Details →
3.1.0 04 Jan 2023 M2 U2 non-standard Yes Details →
3.0.2 29 Nov 2022 M2 U2 non-standard Yes Details →
3.0.1 27 Nov 2022 M2 U2 non-standard Yes Details →
3.0.0 14 Nov 2022 M2 U2 non-standard Yes Details →
2.10.1 09 Sep 2022 M2 U2 non-standard Yes Details →
2.10.0 21 Aug 2022 M2 U2 non-standard Yes Details →
2.9.0 08 Oct 2021 M2 U2 non-standard Yes Details →
2.8.2 14 May 2021 M2 U2 non-standard Yes Details →
2.8.1 29 Oct 2020 M2 U2 non-standard Yes Details →
2.8.0 21 Jun 2020 M2 U2 non-standard Yes Details →
2.7.3 10 Jun 2020 M2 U2 non-standard Yes Details →
2.7.2 02 Dec 2019 M2 U2 non-standard Yes Details →
2.7.1 30 Nov 2019 M2 U2 non-standard Yes Details →
2.7.0 30 Nov 2019 M2 U2 non-standard Yes Details →
2.6.0 11 Jan 2019 M2 U2 non-standard Yes Details →
2.5.2 07 Dec 2017 M2 U2 non-standard Yes Details →
2.4.0 10 Jul 2017 M2 U2 non-standard Yes Details →
2.3.0 24 Apr 2017 M2 U2 non-standard Yes Details →
2.2.6 12 Apr 2017 M2 U2 non-standard Yes Details →
2.2.4 19 Mar 2017 M2 U2 non-standard Yes Details →
2.2.3 20 Dec 2016 M2 U2 non-standard Yes Details →
2.2.2 20 Dec 2016 M2 U2 non-standard Yes Details →
2.2.1 26 Sep 2016 M2 U2 non-standard Yes Details →
2.2.0 25 Sep 2016 M2 U2 non-standard Yes Details →
2.1.4 19 Sep 2016 M2 U2 non-standard Yes Details →
2.0.0 05 Aug 2016 M2 U2 non-standard Yes Details →
1.0.2 01 Aug 2016 M2 U2 non-standard Yes Details →
1.0.1 15 Jul 2016 M2 U2 non-standard Yes Details →
1.0.0 08 Apr 2016 M2 U2 non-standard Yes Details →
0.6.0 24 Mar 2016 M2 U2 non-standard Yes Details →
0.5.0 03 Mar 2016 M2 U2 non-standard Yes Details →
0.4.6 28 Nov 2015 M2 U2 non-standard Yes Details →
0.4.5 08 Nov 2015 M2 U2 non-standard Yes Details →
0.4.4 07 Aug 2015 M2 U2 non-standard Yes Details →
0.4.3 26 Jul 2015 M2 U2 non-standard Yes Details →
0.4.2 24 May 2015 M2 U2 non-standard Yes Details →
0.4.1 21 Apr 2015 M2 U2 non-standard Yes Details →
0.4.0 08 Mar 2015 M2 U2 non-standard Yes Details →
0.3.9 04 Feb 2015 M2 U2 non-standard Yes Details →
0.3.8 04 Feb 2015 M2 U2 non-standard Yes Details →
0.3.7 04 Feb 2015 M2 U2 non-standard Yes Details →
0.3.6 10 Jan 2015 M2 U2 non-standard Yes Details →
0.3.5 23 Dec 2014 M2 U2 non-standard Yes Details →
0.3.4 15 Dec 2014 M2 U2 non-standard Yes Details →
0.3.3 13 Dec 2014 M2 U2 non-standard Yes Details →
0.3.2 12 Dec 2014 M2 U2 non-standard Yes Details →
0.3.1 17 Oct 2014 M2 U2 non-standard Yes Details →
0.3.0 17 Oct 2014 M2 U2 non-standard Yes Details →
0.2.9 15 Oct 2014 M2 U2 non-standard Yes Details →
0.2.8 14 Oct 2014 M2 U2 non-standard Yes Details →
0.2.7 14 Oct 2014 M2 U2 non-standard Yes Details →
0.2.6 13 Oct 2014 M2 U2 non-standard Yes Details →
0.2.5 13 Oct 2014 M2 U2 non-standard Yes Details →
0.2.4 13 Oct 2014 M2 U2 non-standard Yes Details →
0.2.3 13 Oct 2014 M2 U2 non-standard Yes Details →
0.2.2 04 Oct 2014 M2 U2 non-standard Yes Details →
0.2.1 04 Oct 2014 M2 U2 non-standard Yes Details →
0.2.0 03 Oct 2014 M2 U2 non-standard Yes Details →
0.1.9 27 Sep 2014 M2 U2 non-standard Yes Details →
0.1.8 26 Sep 2014 M2 U2 non-standard Yes Details →
0.1.7 26 Sep 2014 M2 U2 non-standard Yes Details →
0.1.6 26 Sep 2014 M2 U2 non-standard Yes Details →
0.1.5 26 Sep 2014 M2 U2 non-standard Yes Details →
0.1.4 26 Sep 2014 M2 U2 non-standard Yes Details →
0.1.3 23 Sep 2014 M2 U2 non-standard Yes Details →
0.1.2 22 Sep 2014 M2 U2 non-standard Yes Details →
0.1.1 22 Sep 2014 M2 U2 non-standard Yes Details →
0.1.0 22 Sep 2014 M2 U2 non-standard Yes Details →
0.0.1 09 Sep 2014 M2 U2 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for signxml

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-48994: SignXML HMAC Signature Verification Vulnerability 6.9 medium 4.0.4 05 Jun 2025
CVE-2025-48995: SignXML HMAC Signature Verification Timing Attack Vulnerability 6.9 medium 4.0.4 05 Jun 2025
CVE-2025-48994: SignXML HMAC Signature Verification Vulnerability 6.9 medium 4.0.4 07 Jul 2026
CVE-2025-48995: SignXML Timing Attack Vulnerability in HMAC Signature Verification 6.9 medium 4.0.4 07 Jul 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 signxml

Is signxml safe to use?

Vulert records 4 vulnerabilities for signxml in PyPI: 0 critical, 0 high, 2 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 signxml's Vulert package health score?

Vulert scores signxml 81/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 signxml affected?

No. 5.2.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 signxml have?

4 vulnerabilities are recorded for signxml in the PyPI ecosystem: 0 critical, 0 high, 2 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 signxml vulnerabilities disclosed?

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

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