VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

gitoxide-core: vulnerability history, versions and safety

gitoxide-core is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 72 releases, first recorded in Aug 2024. 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 L1 U1
i
2 with no fix published

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

See the unfixed vulnerabilities →
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 gitoxide-core vulnerabilities

Vulert verdict on gitoxide-core 0.64.0 i

Updated on 23 Oct 2026

Careful: 0.64.0 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 Sustainable
  • Popularity Key ecosystem project
  • Community Active

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 0.64.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 22 Aug 2024 i
  • Highest CVSS 2.5 i
  • With no published fix 2 i
  • Stars 12,039 i
  • Last release this month i
  • Licence Apache-2.0 OR 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 gitoxide-core, 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.64.0 22 Oct 2026 L1 U1 Apache-2.0 OR MIT No Details →
0.63.0 08 Oct 2026 L1 U1 Apache-2.0 OR MIT No Details →
0.62.0 25 Sep 2026 L1 U1 Apache-2.0 OR MIT No Details →
0.61.1 24 Aug 2026 L1 U1 Apache-2.0 OR MIT No Details →
0.61.0 22 Aug 2026 L1 U1 Apache-2.0 OR MIT No Details →
0.60.0 23 Jul 2026 L1 U1 Apache-2.0 OR MIT No Details →
0.59.0 22 Jun 2026 L1 U1 Apache-2.0 OR MIT No Details →
0.58.0 26 May 2026 L1 U1 Apache-2.0 OR MIT No Details →
0.57.0 27 Apr 2026 L1 U1 Apache-2.0 OR MIT No Details →
0.56.0 24 Apr 2026 L1 U1 Apache-2.0 OR MIT No Details →
0.55.0 22 Mar 2026 L1 U1 Apache-2.0 OR MIT No Details →
0.54.0 22 Feb 2026 L1 U1 Apache-2.0 OR MIT No Details →
0.53.0 22 Jan 2026 L1 U1 Apache-2.0 OR MIT No Details →
0.52.0 31 Dec 2025 L1 U1 Apache-2.0 OR MIT No Details →
0.51.0 22 Dec 2025 L1 U1 Apache-2.0 OR MIT No Details →
0.50.0 22 Nov 2025 L1 U1 Apache-2.0 OR MIT No Details →
0.49.0 22 Oct 2025 L1 U1 Apache-2.0 OR MIT No Details →
0.48.0 15 Jul 2025 L1 U1 Apache-2.0 OR MIT No Details →
0.47.1 26 Apr 2025 L1 U1 Apache-2.0 OR MIT No Details →
0.47.0 25 Apr 2025 L1 U1 Apache-2.0 OR MIT No Details →
0.46.0 04 Apr 2025 L1 U1 Apache-2.0 OR MIT No Details →
0.45.0 18 Jan 2025 L1 U1 Apache-2.0 OR MIT No Details →
0.44.0 22 Dec 2024 L1 U1 Apache-2.0 OR MIT No Details →
0.43.0 24 Nov 2024 L1 U1 Apache-2.0 OR MIT No Details →
0.42.0 22 Oct 2024 L1 U1 Apache-2.0 OR MIT No Details →
0.41.0 22 Aug 2024 L1 U1 Apache-2.0 OR MIT No Details →
0.40.0 22 Aug 2024 L1 U1 Apache-2.0 OR MIT No Details →
0.39.1 25 Jul 2024 L1 U1 Apache-2.0 OR MIT No Details →
0.39.0 23 Jul 2024 L1 U1 Apache-2.0 OR MIT No Details →
0.38.0 22 May 2024 L1 U1 Apache-2.0 OR MIT No Details →
0.37.0 13 Apr 2024 L1 U1 Apache-2.0 OR MIT No Details →
0.36.0 25 Feb 2024 L1 U1 Apache-2.0 OR MIT No Details →
0.35.0 29 Dec 2023 L1 U1 Apache-2.0 OR MIT No Details →
0.34.0 06 Dec 2023 L1 U1 Apache-2.0 OR MIT No Details →
0.33.1 13 Oct 2023 L1 U1 Apache-2.0 OR MIT No Details →
0.33.0 12 Oct 2023 L1 U1 Apache-2.0 OR MIT No Details →
0.32.0 24 Sep 2023 L1 U1 Apache-2.0 OR MIT No Details →
0.31.0 22 Aug 2023 L1 U1 Apache-2.0 OR MIT No Details →
0.30.0 22 Jul 2023 L1 U1 Apache-2.0 OR MIT No Details →
0.29.0 22 Jun 2023 L1 U1 Apache-2.0 OR MIT No Details →
0.28.0 07 Jun 2023 L1 U1 Apache-2.0 OR MIT No Details →
0.27.0 27 Apr 2023 L1 U1 Apache-2.0 OR MIT No Details →
0.26.0 27 Apr 2023 L1 U1 Apache-2.0 OR MIT No Details →
0.25.0 24 Feb 2023 L1 U1 Apache-2.0 OR MIT No Details →
0.24.0 17 Feb 2023 L1 U1 Apache-2.0 OR MIT No Details →
0.23.0 09 Feb 2023 L1 U1 Apache-2.0 OR MIT No Details →
0.22.0 22 Dec 2022 L1 U1 Apache-2.0 OR MIT No Details →
0.21.0 21 Nov 2022 L1 U1 Apache-2.0 OR MIT No Details →
0.20.0 17 Nov 2022 L1 U1 Apache-2.0 OR MIT No Details →
0.19.0 06 Nov 2022 L1 U1 Apache-2.0 OR MIT No Details →
0.18.0 20 Sep 2022 L1 U1 Apache-2.0 OR MIT No Details →
0.17.0 24 Aug 2022 L1 U1 Apache-2.0 OR MIT No Details →
0.16.0 17 Aug 2022 L1 U1 Apache-2.0 OR MIT No Details →
0.15.0 22 Jul 2022 L1 U1 Apache-2.0 OR MIT No Details →
0.14.0 05 Apr 2022 L1 U1 Apache-2.0 OR MIT No Details →
0.13.0 03 Apr 2022 L1 U1 Apache-2.0 OR MIT No Details →
0.12.0 19 Oct 2021 L1 U1 Apache-2.0 OR MIT No Details →
0.11.0 15 Oct 2021 L1 U1 Apache-2.0 OR MIT No Details →
0.10.5 10 Sep 2021 L1 U1 Apache-2.0 OR MIT No Details →
0.10.4 07 Sep 2021 L1 U1 Apache-2.0 OR MIT No Details →
0.10.3 29 Aug 2021 L1 U1 Apache-2.0 OR MIT No Details →
0.10.2 17 Aug 2021 L1 U1 Apache-2.0 OR MIT No Details →
0.10.1 15 Aug 2021 L1 U1 Apache-2.0 OR MIT No Details →
0.10.0 10 Aug 2021 L1 U1 Apache-2.0 OR MIT No Details →
0.9.0 09 May 2021 L1 U1 Apache-2.0 OR MIT No Details →
0.8.0 08 Apr 2021 L1 U1 Apache-2.0 OR MIT No Details →
0.7.0 16 Dec 2020 L1 U1 Apache-2.0 OR MIT No Details →
0.6.0 15 Dec 2020 L1 U1 Apache-2.0 OR MIT No Details →
0.4.1 18 Sep 2020 L1 U1 Apache-2.0 OR MIT No Details →
0.4.0 12 Sep 2020 L1 U1 Apache-2.0 OR MIT No Details →
0.3.0 12 Aug 2020 L1 U1 MIT No Details →
0.1.0 12 Jul 2020 L1 U1 MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2

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

03 Vulnerabilities

Recorded vulnerabilities for gitoxide-core

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-43785: gitoxide-core does not neutralize special characters for terminals 2.5 low No fix published 22 Aug 2024
Insecure Handling of Special Characters in gitoxide-core 2.5 low No fix published 22 Aug 2024

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 gitoxide-core

Is gitoxide-core safe to use?

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

Vulert scores gitoxide-core 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 gitoxide-core affected?

Yes. 0.64.0, 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 gitoxide-core have?

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

0 vulnerabilities were recorded for gitoxide-core in the last 12 months, and the oldest entry in this database dates to 22 Aug 2024. 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 gitoxide-core 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 gitoxide-core for upcoming vulnerabilities?

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