openc3 (rubygems) has 11 known vulnerabilities, the worst rated CRITICAL. Upgrade to 7.3.0 or later to clear all of them. No malicious-package signal is recorded.
COSMOS reads configuration from a user-writable overlay (targetsmodified/) before the read-only plugin-installed targets/ tree, and the config subsystem…
CyberXYZ does not call a package safe in absolute terms. It records 11 known vulnerabilities for openc3 (rubygems), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does openc3 have known vulnerabilities?
Yes. CyberXYZ records 11 known vulnerabilities for openc3 (rubygems), the worst rated CRITICAL. These include GHSA-jjq7-m736-w977, GHSA-v529-vhwc-wfc5, GHSA-2wvh-87g2-89hr, GHSA-w757-4qv9-mghp, GHSA-vp3w-52v9-q57f.
Which version of openc3 should I use?
7.3.0 or later clears every advisory recorded for openc3 (rubygems). Check the release you pick before installing it.
How do I check openc3 before installing?
Search openc3 in CyberXYZ Check at https://cyberxyz.io/check?q=openc3. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 11:38 UTC. The most recent advisory here was published 2026-09-23. Updated continuously from NVD, GHSA, OSV and CNA feeds.