VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

openc3: vulnerability history, versions and safety

openc3 is a package in the PyPI ecosystem. Vulert records 15 vulnerabilities for it across 61 releases, from Oct 2024 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
15 vulnerabilities recorded U15
i
7 with no fix published

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

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

Most recent disclosure 04 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all openc3 vulnerabilities

Vulert verdict on openc3 7.4.1 i

Updated on 23 Oct 2026

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

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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 7.4.1 — affected i
  • Vulnerabilities on record 15 over 1 year · 5 in the last year i
  • Latest disclosure 04 May 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 7 i
  • Stars 256 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 openc3, 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
7.4.1 24 Sep 2026 U8 non-standard No Details →
7.4.0 11 Sep 2026 U8 non-standard No Details →
7.3.0 07 Aug 2026 U8 non-standard No Details →
7.2.1 11 Jul 2026 U8 non-standard No Details →
7.2.0 01 Jun 2026 U8 non-standard No Details →
7.1.1 15 May 2026 U2 non-standard No Details →
6.10.6 04 May 2026 U5 — No Details →
7.1.0 30 Apr 2026 U2 non-standard No Details →
6.10.5 12 Apr 2026 U5 — No Details →
7.0.1 10 Apr 2026 U2 non-standard No Details →
7.0.0 26 Mar 2026 U2 non-standard No Details →
7.0.0rc3 06 Mar 2026 U5 non-standard No Details →
7.0.0rc2 19 Feb 2026 U5 non-standard No Details →
6.10.4 10 Jan 2026 U7 — No Details →
6.10.3 30 Dec 2025 U7 — No Details →
6.10.2 16 Dec 2025 U7 — No Details →
6.10.1 10 Dec 2025 U7 — No Details →
6.10.0 10 Dec 2025 U7 — No Details →
6.9.2 05 Nov 2025 U7 — No Details →
6.9.1 05 Oct 2025 U7 — No Details →
6.9.0 03 Oct 2025 U7 — No Details →
6.8.1 13 Sep 2025 U7 — No Details →
6.8.0 12 Sep 2025 U7 — No Details →
6.7.0 05 Aug 2025 U7 — No Details →
6.6.0 08 Jul 2025 U6 — No Details →
6.5.1 30 Jun 2025 U6 — No Details →
6.5.0 13 Jun 2025 U6 — No Details →
6.4.2 30 May 2025 U6 — No Details →
6.4.1 14 May 2025 U6 — No Details →
6.4.0 07 May 2025 U6 — No Details →
6.3.0 05 Apr 2025 U6 — No Details →
6.2.1 07 Mar 2025 U6 — No Details →
6.2.0 01 Mar 2025 U6 — No Details →
6.1.0 05 Feb 2025 U6 — No Details →
6.0.2 09 Jan 2025 U6 — No Details →
6.0.1 20 Dec 2024 U6 — No Details →
6.0.0 17 Dec 2024 U11 — No Details →
5.20.0 31 Oct 2024 U11 — No Details →
5.19.0 01 Oct 2024 U11 — No Details →
5.18.0 19 Aug 2024 U14 — No Details →
5.17.1 27 Jun 2024 U14 — No Details →
5.17.0 26 Jun 2024 U14 — No Details →
5.16.2 29 May 2024 U14 — No Details →
0.1.0 23 May 2024 U14 — No Details →
5.16.1 09 May 2024 U14 non-standard No Details →
5.16.0 04 May 2024 U14 non-standard No Details →
5.15.2 01 Apr 2024 U14 non-standard No Details →
5.15.1 15 Mar 2024 U14 non-standard No Details →
5.15.0 10 Mar 2024 U14 non-standard No Details →
5.14.2 11 Feb 2024 U14 non-standard No Details →
5.14.1 25 Jan 2024 U14 non-standard No Details →
5.14.0 19 Jan 2024 U14 non-standard No Details →
5.13.0 18 Dec 2023 U14 non-standard No Details →
5.12.0 10 Nov 2023 U14 non-standard No Details →
5.11.3 10 Oct 2023 U14 non-standard No Details →
5.11.2 03 Oct 2023 U14 non-standard No Details →
5.11.1 30 Sep 2023 U14 non-standard No Details →
5.11.0 18 Sep 2023 U14 non-standard No Details →
5.10.1 17 Aug 2023 U14 non-standard No Details →
5.10.0 05 Aug 2023 U14 non-standard No Details →
5.9.2b0 04 Aug 2023 U14 non-standard No Details →

All 61 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 3
  • 2025 7
  • 2026 5

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

03 Vulnerabilities

Recorded vulnerabilities for openc3

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-28388: OpenC3 COSMOS Hardcoded Credentials Vulnerability 9.8 critical No fix published 13 Jun 2025
CVE-2025-28389: OpenC3 COSMOS v6.0.0 Weak Password Requirements Allow Brute Force Authentication Bypass 9.8 critical No fix published 13 Jun 2025
CVE-2025-28386: OpenC3 Plugin Management Remote Code Execution Vulnerability 9.8 critical No fix published 13 Jun 2025
CVE-2026-42087: OpenC3 SQL Injection Vulnerability in Time-Series Database Component 9.6 critical 7.0.0 04 May 2026
CVE-2025-28384: OpenC3 COSMOS Directory Traversal Vulnerability 9.1 critical No fix published 13 Jun 2025

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 openc3

Is openc3 safe to use?

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

What is openc3's Vulert package health score?

Vulert scores openc3 50/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 openc3 affected?

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

Which version of openc3 should I use?

7.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 openc3 have?

15 vulnerabilities are recorded for openc3 in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 15 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 openc3 vulnerabilities disclosed?

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

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