How severe is CVE-2024-43795?

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

Which packages are affected by CVE-2024-43795?

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

How do I fix CVE-2024-43795?

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-43795 is resolved across your whole dependency graph.

How do I detect CVE-2024-43795 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-43795 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2024-43795?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-43795 can be triaged on real exposure rather than presence alone.

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

No public exploit code has been indexed for CVE-2024-43795 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

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

CVE-2024-43795 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th 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-43795?

CVE-2024-43795 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2024-43795 was published on October 2, 2024 and was last updated on August 12, 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-43795 — @openc3/tool-common

Fix: OpenC3/cosmos@762d7e0

CVE-2024-43795 is a Cross-site Scripting (XSS) vulnerability in @openc3/tool-common. A fix is available for @openc3/tool-common — see the affected versions and patch details below.

OpenC3 COSMOS vulnerable to cross-site scripting in Login functionality (`GHSL-2024-128`)

Also known asGHSA-vfj8-5pj7-2f9gPYSEC-2024-100

Published

Oct 2, 2024

Updated

Aug 12, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 20, 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-43795.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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

67downloads / week

Description

OpenC3 COSMOS provides the functionality needed to send commands to and receive data from one or more embedded systems. The login functionality contains a reflected cross-site scripting (XSS) vulnerability. This vulnerability is fixed in 5.19.0. Note: This CVE 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`

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-43795 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-43795 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2024-43795. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-43795 in your dependencies?

O3 Security finds CVE-2024-43795 across npm, PyPI, RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score