VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

cobbler: vulnerability history, versions and safety

cobbler is a package in the PyPI ecosystem. Vulert records 36 vulnerabilities for it across 29 releases, from Oct 2021 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
36 vulnerabilities recorded C4 H9 M5 U18
i
4 with no fix published

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

See the unfixed vulnerabilities →
i
12 in the last 12 months

Most recent disclosure 06 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all cobbler vulnerabilities

Vulert verdict on cobbler 3.3.10 i

Updated on 23 Oct 2026

Careful: 3.3.10 has 5 known vulnerabilities, and 4 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 54/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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 3.3.10 — affected i
  • Vulnerabilities on record 36 over 4 years · 12 in the last year i
  • Latest disclosure 06 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 4 i
  • Stars 2,775 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago 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 cobbler, 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
4.0.0b7 22 Oct 2026 M2 U3 non-standard No Details →
3.3.10 18 Sep 2026 M2 U3 non-standard No Details →
4.0.0b6 31 Aug 2026 M2 U3 non-standard No Details →
3.3.9 29 Aug 2026 M2 U3 non-standard No Details →
4.0.0b5 27 Aug 2026 M2 U3 non-standard No Details →
4.0.0b4 27 Aug 2026 M2 U3 non-standard No Details →
4.0.0b3 26 Aug 2026 M2 U3 non-standard No Details →
4.0.0b2 25 Aug 2026 M2 U3 non-standard No Details →
4.0.0b1 16 Aug 2026 M2 U3 non-standard No Details →
4.0.0a9 16 Aug 2026 M2 U3 non-standard No Details →
4.0.0a8 16 Aug 2026 M2 U3 non-standard No Details →
4.0.0a7 14 Aug 2026 M2 U3 non-standard No Details →
4.0.0a6 14 Aug 2026 M2 U3 non-standard No Details →
4.0.0a5 13 Aug 2026 M2 U3 non-standard No Details →
4.0.0a4 16 Jul 2026 M2 U3 non-standard No Details →
4.0.0a3 15 Jul 2026 M2 U3 non-standard No Details →
4.0.0a2 08 Jul 2026 M2 U3 non-standard No Details →
3.2.3 17 Nov 2024 M1 non-standard Yes Details →
3.3.7 17 Nov 2024 M2 U3 non-standard No Details →
3.3.6 16 Jul 2024 C1 non-standard Yes Details →
3.3.5 05 Jul 2024 C1 non-standard Yes Details →
3.3.4 26 Feb 2024 C1 non-standard Yes Details →
3.3.3 03 Jun 2022 C1 non-standard Yes Details →
3.3.2 11 Mar 2022 C1 non-standard Yes Details →
3.3.1 18 Feb 2022 C1 M1 U1 non-standard Yes Details →
3.2.2 21 Sep 2021 H5 M1 U7 non-standard Yes Details →
3.3.0 21 Sep 2021 C1 H2 M1 U3 non-standard Yes Details →
3.2.1 04 Mar 2021 H5 M1 U7 non-standard Yes Details →
3.1.2 27 May 2020 H5 M1 U7 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 6
  • 2022 17
  • 2024 1
  • 2026 12

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

03 Vulnerabilities

Recorded vulnerabilities for cobbler

The 5 most severe of 36 vulnerabilities recorded for this package

Search all 36 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-47533: Cobbler XML-RPC Server Vulnerability Allows Unauthorized Access 9.8 critical 3.2.3 29 Jun 2026
CVE-2018-10931: Cobbler Exposed Dangerous Method or Function 9.8 critical 3.0.0 13 May 2022
CVE-2018-10931: Cobbler Package Exposes Dangerous Method via XMLRPC 9.8 critical 3.0.0 29 Jun 2026
CVE-2018-1000226: Cobbler Improper Validation of Security Tokens Vulnerability 9.8 critical 3.0.0 29 Jun 2026
CVE-2017-1000469: Cobbler Arbitrary Code Execution Vulnerability 9.8 critical 3.0.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 cobbler

Is cobbler safe to use?

Vulert records 36 vulnerabilities for cobbler in PyPI: 4 critical, 9 high, 5 medium and 0 low, plus 18 not yet rated. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is cobbler's Vulert package health score?

Vulert scores cobbler 54/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 cobbler affected?

Yes. 3.3.10, the version you would install today, has 5 known vulnerabilities, and 4 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of cobbler should I use?

3.3.10 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 cobbler have?

36 vulnerabilities are recorded for cobbler in the PyPI ecosystem: 4 critical, 9 high, 5 medium and 0 low, plus 18 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 cobbler vulnerabilities disclosed?

12 vulnerabilities were recorded for cobbler in the last 12 months, and the oldest entry in this database dates to 04 Oct 2021. 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 cobbler 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 cobbler for upcoming vulnerabilities?

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