NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2024-28397 — js2py

HIGHFix: PiotrDabkowski/Js2Py#323

CVE-2024-28397 is a high-severity (CVSS 8.8) Code Injection vulnerability in js2py. 6 public exploit or proof-of-concept references are indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

js2py allows remote code execution

Also known asPYSEC-2026-1476
Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
6 known
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

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

EPSS Exploitation Probability

via FIRST.org ↗
4.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk
0.00%25.3%50.5%75.8%48.4%4.5%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐍js2py

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

An issue in the component js2py.disable_pyimport() of js2py up to v0.74 allows attackers to execute arbitrary code via a crafted API call.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐍PyPIjs2pyall versionsNo fix
Exploits & PoCs
6

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

EDB-52532webappsmultiple

Js2Py 0.74 - RCE

by alisunbul · Apr 30, 2026

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Remediation status

    The records we use list no patched version of js2py for CVE-2024-28397. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

How to detect CVE-2024-28397

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2024-28397 -u https://target
Template
pyload-ng js2py - Remote Code Execution
Severity
medium
Impact
Attackers can execute arbitrary code on the server through malicious JavaScript code execution via js2py.
Remediation
Update pyload-ng to a version that removes or secures the js2py dependency.

Template by ProjectDiscovery nuclei-templates (iamnoooob, rootxharsh, pdresearch), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

An issue in the component `js2py.disable_pyimport()` of js2py up to v0.74 allows attackers to execute arbitrary code via a crafted API call.
O3 Security · Impact-Aware SCA

Is CVE-2024-28397 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2024-28397: js2py RCE (High 8.8)