VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/moov-io/signedxml: vulnerability history, versions and safety

github.com/moov-io/signedxml is a package in the Go ecosystem. Vulert records 4 vulnerabilities for it across 60 releases, from May 2023 to Oct 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 C1 H1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 21 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/moov-io/signedxml vulnerabilities

Vulert verdict on github.com/moov-io/signedxml v1.4.1 i

Updated on 23 Oct 2026

Action needed: v1.4.1 has 4 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

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

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v1.4.1 — affected i
  • Vulnerabilities on record 4 over 3 years · 1 in the last year i
  • Latest disclosure 21 Oct 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Stars 66 i
  • OpenSSF scorecard 6/10 i
  • Last release 1 month ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, 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 github.com/moov-io/signedxml, 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
v1.4.2-0.20261020144633-77ceb667cecb 20 Oct 2026 C1 H1 U2 MIT Yes Details →
v1.4.2-0.20261014145950-17003e085b08 14 Oct 2026 C1 H1 U2 MIT Yes Details →
v1.4.2-0.20261009194029-e36c0731e471 09 Oct 2026 C1 H1 U2 MIT Yes Details →
v1.4.1 26 Aug 2026 C1 H1 U2 MIT Yes Details →
v1.4.1-0.20260826140957-da2cd6126c4c 26 Aug 2026 C1 H1 U2 MIT Yes Details →
v1.4.1-0.20260825205754-f612012af643 25 Aug 2026 C1 H1 U2 MIT Yes Details →
v1.4.0 18 Aug 2026 C1 H1 U2 MIT Yes Details →
v1.3.2-0.20260813204814-1811347f38e6 13 Aug 2026 C1 H1 U2 MIT Yes Details →
v1.3.1 13 Aug 2026 C1 H1 U2 MIT Yes Details →
v1.3.1-0.20260608195304-3447aceab949 08 Jun 2026 C1 H1 U2 MIT Yes Details →
v1.3.1-0.20260522014352-93b98bf491de 22 May 2026 C1 H1 U2 MIT Yes Details →
v1.3.0 02 Apr 2026 C1 H1 U2 MIT Yes Details →
v1.2.6-0.20260326212710-eb57498adebc 26 Mar 2026 C1 H1 U2 MIT Yes Details →
v1.2.6-0.20260326210113-76ea6a0bb6dc 26 Mar 2026 C1 H1 U2 MIT Yes Details →
v1.2.6-0.20260326205944-fe1339a9ce7c 26 Mar 2026 C1 H1 U2 MIT Yes Details →
v1.2.6-0.20260326205849-5759c43c6390 26 Mar 2026 C1 H1 U2 MIT Yes Details →
v1.2.5 06 Jan 2026 C1 H1 U2 MIT Yes Details →
v1.2.5-0.20260106230919-dbc23dc7b721 06 Jan 2026 C1 H1 U2 MIT Yes Details →
v1.2.4-0.20250627115550-a03ea9778463 27 Jun 2025 C1 H1 U2 MIT Yes Details →
v1.2.4-0.20250401165710-13000a3dfd10 01 Apr 2025 C1 H1 U2 MIT Yes Details →
v1.2.3 20 Mar 2025 C1 H1 U2 MIT Yes Details →
v1.2.3-0.20250211202329-94f1540f0a77 11 Feb 2025 C1 H1 U2 MIT Yes Details →
v1.2.3-0.20241203191326-924f5be533c2 03 Dec 2024 C1 H1 U2 MIT Yes Details →
v1.2.3-0.20241123125259-8b1b6f5da543 23 Nov 2024 C1 H1 U2 MIT Yes Details →
v1.2.3-0.20241107000508-123a311adb38 07 Nov 2024 C1 H1 U2 MIT Yes Details →
v1.2.3-0.20241002134150-33e2cd997abf 02 Oct 2024 C1 H1 U2 MIT Yes Details →
v1.2.3-0.20240815181552-e77aa738ad87 15 Aug 2024 C1 H1 U2 MIT Yes Details →
v1.2.3-0.20240815125924-158edc4f13a5 15 Aug 2024 C1 H1 U2 MIT Yes Details →
v1.2.3-0.20240812152851-7f8f17a54a68 12 Aug 2024 C1 H1 U2 MIT Yes Details →
v1.2.3-0.20240806201127-2f89e2255094 06 Aug 2024 C1 H1 U2 MIT Yes Details →
v1.2.3-0.20240717180338-e14c3b87da7e 17 Jul 2024 C1 H1 U2 MIT Yes Details →
v1.2.2 10 Jun 2024 C1 H1 U2 MIT Yes Details →
v1.2.2-0.20240610181932-25d4163de3c2 10 Jun 2024 C1 H1 U2 MIT Yes Details →
v1.2.2-0.20240610180431-17cecbf0cef1 10 Jun 2024 C1 H1 U2 MIT Yes Details →
v1.2.2-0.20240515135147-c2bbfb123203 15 May 2024 C1 H1 U2 MIT Yes Details →
v1.2.2-0.20240507162501-fcb25cb500bd 07 May 2024 C1 H1 U2 MIT Yes Details →
v1.2.1 20 Mar 2024 C1 H1 U2 MIT Yes Details →
v1.2.1-0.20240320190224-9b88aa446745 20 Mar 2024 C1 H1 U2 MIT Yes Details →
v1.2.1-0.20240317160505-fa75a13b00f4 17 Mar 2024 C1 H1 U2 MIT Yes Details →
v1.1.2-0.20240219194815-9757d76d3669 19 Feb 2024 C1 H1 U2 MIT Yes Details →
v1.2.0 19 Feb 2024 C1 H1 U2 MIT Yes Details →
v1.1.2-0.20240219160444-130303b1af6c 19 Feb 2024 C1 H1 U2 MIT Yes Details →
v1.1.2-0.20240102153139-24380761ec05 02 Jan 2024 C1 H1 U2 MIT Yes Details →
v0.0.0-20230801140620-88b12dfd4b0a 01 Aug 2023 C1 H1 U2 MIT Yes Details →
v1.1.2-0.20230801140620-88b12dfd4b0a 01 Aug 2023 C1 H1 U2 MIT Yes Details →
v0.0.0-20230629134500-6cf4f6de4822 29 Jun 2023 C1 H1 U2 MIT Yes Details →
v1.1.2-0.20230629134500-6cf4f6de4822 29 Jun 2023 C1 H1 U2 MIT Yes Details →
v1.1.1 08 Jun 2023 C1 H1 U2 MIT Yes Details →
v1.1.1-0.20230608143421-55338321683f 08 Jun 2023 C1 H1 U2 MIT Yes Details →
v1.1.1-0.20230608021838-a2f8879ab59c 08 Jun 2023 C1 H1 U2 MIT Yes Details →
v1.1.0 30 May 2023 C1 H1 U2 MIT Yes Details →
v1.0.1-0.20230530175933-ec2ea1760f95 30 May 2023 C1 H1 U2 MIT Yes Details →
v1.0.0 21 Apr 2023 C1 H1 U2 MIT Yes Details →
v0.0.0-20230421171937-f733fc892c85 21 Apr 2023 C1 H1 U2 MIT Yes Details →
v0.0.0-20230421170133-755d77df1573 21 Apr 2023 C1 H1 U2 MIT Yes Details →
v0.0.0-20230421165858-0b702abaf8e1 21 Apr 2023 C1 H1 U2 MIT Yes Details →
v0.0.0-20230421165844-3d0a62f8eb2d 21 Apr 2023 C1 H1 U2 MIT Yes Details →
v0.0.0-20210628192057-abc5b481ae1c 28 Jun 2021 C1 H1 U2 MIT Yes Details →
v0.0.0-20200709203052-5961fe7b44fd 09 Jul 2020 C1 H1 U2 MIT Yes Details →
v0.0.0-20200706235130-1ca905e228f0 06 Jul 2020 C1 H1 U2 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 3
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/moov-io/signedxml

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-34205: Signature validation bypass in github.com/moov-io/signedxml 9.1 critical 1.1.0 30 May 2023
CVE-2026-113729: Moov signedxml Unauthenticated Denial of Service in Exclusive XML Canonicalization 7.5 high 1.4.1 21 Oct 2026
CVE-2023-34205: Signature validation bypass in github.com/moov-io/signedxml N/A unrated 1.1.0 09 Jun 2023
CVE-2023-34205: Signature validation bypass in github.com/moov-io/signedxml N/A unrated 1.1.0 09 Jun 2023

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 github.com/moov-io/signedxml

Is github.com/moov-io/signedxml safe to use?

Vulert records 4 vulnerabilities for github.com/moov-io/signedxml in Go: 1 critical, 1 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 github.com/moov-io/signedxml's Vulert package health score?

Vulert scores github.com/moov-io/signedxml 72/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 github.com/moov-io/signedxml affected?

Yes. v1.4.1, the version you would install today, has 4 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/moov-io/signedxml should I use?

v1.4.1 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 github.com/moov-io/signedxml have?

4 vulnerabilities are recorded for github.com/moov-io/signedxml in the Go ecosystem: 1 critical, 1 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 github.com/moov-io/signedxml vulnerabilities disclosed?

1 vulnerability was recorded for github.com/moov-io/signedxml in the last 12 months, and the oldest entry in this database dates to 30 May 2023. 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 github.com/moov-io/signedxml 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 github.com/moov-io/signedxml for upcoming vulnerabilities?

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