VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

pulpcore: vulnerability history, versions and safety

pulpcore is a package in the PyPI ecosystem. Vulert records 3 vulnerabilities for it across 120 releases, from May 2022 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
3 vulnerabilities recorded H1 M1 U1
i
3 with no fix published

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

See the unfixed vulnerabilities →
i
1 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 pulpcore vulnerabilities

Vulert verdict on pulpcore 3.123.0 i

Updated on 23 Oct 2026

Careful: 3.123.0 has 3 known vulnerabilities, and 3 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 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.123.0 — affected i
  • Vulnerabilities on record 3 over 4 years · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 6.7 i
  • With no published fix 3 i
  • Depended on by 17 packages i
  • Stars 611 i
  • Last release this month i
  • Licence GPL-2.0-or-later 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 pulpcore, 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
3.105.24 22 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.85.33 22 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.73.46 22 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.63.49 22 Oct 2026 H1 M1 U1 non-standard No Details →
3.49.72 22 Oct 2026 H1 M1 U1 non-standard No Details →
3.115.5 21 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.112.2 21 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.118.4 21 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.123.0 21 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.118.3 15 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.23 15 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.122.2 15 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.122.1 15 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.122.0 14 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.85.32 14 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.22 14 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.118.2 13 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.121.3 09 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.121.2 08 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.121.1 08 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.121.0 06 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.21 01 Oct 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.120.0 29 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.119.2 29 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.49.71 24 Sep 2026 H1 M1 U1 non-standard No Details →
3.63.48 24 Sep 2026 H1 M1 U1 non-standard No Details →
3.73.45 24 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.85.31 23 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.20 23 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.119.1 23 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.119.0 23 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.118.1 17 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.118.0 15 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.117.2 11 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.117.1 04 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.49.70 02 Sep 2026 H1 M1 U1 non-standard No Details →
3.63.47 02 Sep 2026 H1 M1 U1 non-standard No Details →
3.73.44 02 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.116.3 02 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.19 02 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.117.0 02 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.49.69 01 Sep 2026 H1 M1 U1 non-standard No Details →
3.63.46 01 Sep 2026 H1 M1 U1 non-standard No Details →
3.85.30 01 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.73.43 01 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.18 01 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.116.2 01 Sep 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.116.1 27 Aug 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.17 27 Aug 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.116.0 12 Aug 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.16 12 Aug 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.115.4 12 Aug 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.85.29 12 Aug 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.63.45 29 Jul 2026 H1 M1 U1 non-standard No Details →
3.49.68 29 Jul 2026 H1 M1 U1 non-standard No Details →
3.73.42 29 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.85.28 29 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.115.3 28 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.15 28 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.85.27 28 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.73.41 28 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.63.44 28 Jul 2026 H1 M1 U1 non-standard No Details →
3.49.67 28 Jul 2026 H1 M1 U1 non-standard No Details →
3.105.14 28 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.13 27 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.115.2 22 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.115.1 21 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.115.0 21 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.63.43 20 Jul 2026 H1 M1 U1 non-standard No Details →
3.73.40 20 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.49.66 20 Jul 2026 H1 M1 U1 non-standard No Details →
3.85.26 20 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.12 20 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.114.2 20 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.11 16 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.85.25 16 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.73.39 16 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.63.42 16 Jul 2026 H1 M1 U1 non-standard No Details →
3.49.65 16 Jul 2026 H1 M1 U1 non-standard No Details →
3.85.24 14 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.114.1 14 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.10 14 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.73.38 14 Jul 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.63.41 14 Jul 2026 H1 M1 U1 non-standard No Details →
3.49.64 14 Jul 2026 H1 M1 U1 non-standard No Details →
3.49.63 09 Jun 2026 U1 non-standard No Details →
3.85.23 09 Jun 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.73.37 09 Jun 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.114.0 09 Jun 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.9 09 Jun 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.113.0 03 Jun 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.85.22 03 Jun 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.112.1 03 Jun 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.8 03 Jun 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.73.36 03 Jun 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.63.40 03 Jun 2026 H1 M1 U1 non-standard No Details →
3.49.62 03 Jun 2026 U1 non-standard No Details →
3.111.2 19 May 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.112.0 19 May 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.111.1 14 May 2026 H1 M1 U1 GPL-2.0-or-later No Details →
3.105.7 13 May 2026 H1 M1 U1 — No Details →
3.63.39 13 May 2026 H1 M1 U1 — No Details →
3.73.35 13 May 2026 H1 M1 U1 — No Details →
3.85.21 13 May 2026 H1 M1 U1 — No Details →
3.110.3 13 May 2026 H1 M1 U1 — No Details →
3.111.0 13 May 2026 H1 M1 U1 — No Details →
3.85.20 07 May 2026 H1 M1 U1 — No Details →
3.73.34 07 May 2026 H1 M1 U1 — No Details →
3.63.38 07 May 2026 H1 M1 U1 — No Details →
3.49.61 07 May 2026 U1 — No Details →
3.110.2 07 May 2026 H1 M1 U1 — No Details →
3.49.60 05 May 2026 U1 — No Details →
3.73.33 05 May 2026 H1 M1 U1 — No Details →
3.63.37 05 May 2026 H1 M1 U1 — No Details →
3.85.19 05 May 2026 H1 M1 U1 — No Details →
3.105.6 05 May 2026 H1 M1 U1 — No Details →
3.110.1 05 May 2026 H1 M1 U1 — No Details →
3.110.0 28 Apr 2026 H1 M1 U1 — No Details →
3.109.3 28 Apr 2026 H1 M1 U1 — No Details →
3.105.5 28 Apr 2026 H1 M1 U1 — No Details →

The newest 120 of 791 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2024 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for pulpcore

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Pulpcore: Incorrect RBAC Permission Assignment in Object Creation Tasks 6.7 high No fix published 07 Aug 2024
CVE-2024-7143: pulpcore - RBAC Permissions Misassignment in Task Object Creation 6.7 medium No fix published 07 Jul 2026
CVE-2018-10917: Pulp Improper Path Parsing 6.5 medium No fix published 13 May 2022

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 pulpcore

Is pulpcore safe to use?

Vulert records 3 vulnerabilities for pulpcore in PyPI: 0 critical, 1 high, 1 medium and 0 low, plus 1 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is pulpcore's Vulert package health score?

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

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

How many vulnerabilities does pulpcore have?

3 vulnerabilities are recorded for pulpcore in the PyPI ecosystem: 0 critical, 1 high, 1 medium and 0 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 pulpcore vulnerabilities disclosed?

1 vulnerability was recorded for pulpcore in the last 12 months, and the oldest entry in this database dates to 13 May 2022. 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 pulpcore 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 pulpcore for upcoming vulnerabilities?

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