How severe is CVE-2024-47529?

No CVSS score has been assigned to CVE-2024-47529 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-47529?

CVE-2024-47529 affects the following packages: @openc3/tool-common (npm), openc3 (PyPI), openc3 (RubyGems). Ecosystems affected: npm, PyPI, RubyGems.

How do I fix CVE-2024-47529?

Update @openc3/tool-common to 5.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-47529 is resolved across your whole dependency graph.

How do I detect CVE-2024-47529 in my npm, PyPI, RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openc3/tool-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-47529 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2024-47529 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2024-47529, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-47529?

CVE-2024-47529 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 29th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-47529?

CVE-2024-47529 is classified as CWE-312 (CWE-312). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-47529 published, and has it been updated?

CVE-2024-47529 was published on October 2, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm🐍 PyPI💎 RubyGems

Not in CISA KEV

CVE-2024-47529 — @openc3/tool-common

Fix: OpenC3/cosmos@b5ab34f

CVE-2024-47529 is a CWE-312 vulnerability in @openc3/tool-common. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for @openc3/tool-common — see the affected versions and patch details below.

OpenC3 COSMOS uses clear text storage of password/token (`GHSL-2024-129`)

Also known asGHSA-4xqv-47rm-37mmPYSEC-2024-121

Published

Oct 2, 2024

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-47529.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@openc3/tool-commonnpm

160downloads / week

Description

OpenC3 COSMOS provides the functionality needed to send commands to and receive data from one or more embedded systems. OpenC3 COSMOS stores the password of a user unencrypted in the LocalStorage of a web browser. This makes the user password susceptible to exfiltration via Cross-site scripting (see GHSL-2024-128). This vulnerability is fixed in 5.19.0. This only affects Open Source edition, and not OpenC3 COSMOS Enterprise Edition.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@openc3/tool-common`	all versions	5.19.0`npm install @openc3/tool-common@5.19.0`
🐍PyPI	`openc3`	all versions	5.19.0`pip install --upgrade 'openc3==5.19.0'`
💎RubyGems	`openc3`	all versions	5.19.0`bundle update openc3 --conservative`

Affected Products

1 product · 1 configurations

Application

cosmosopenc3

< 5.19.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

OpenC3 COSMOS provides the functionality needed to send commands to and …

securitylab.github.comNVDNov 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openc3/tool-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @openc3/tool-common to 5.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-47529 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-47529 in your dependencies?

Find it across npm, PyPI, RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works