CVE-2024-36857 — @janhq/core
HIGHCVE-2024-36857 is a high-severity (CVSS 7.5) CWE-31 vulnerability in @janhq/core. 1 public exploit or proof-of-concept reference is 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.
Jan path traversal vulnerability
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.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-36857.
EPSS Exploitation Probability
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
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.
@janhq/corenpmDescription
Jan v0.4.12 was discovered to contain an arbitrary file read vulnerability via the /v1/app/readFileSync interface.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @janhq/core | all versions | No fix |
Affected Products
janhomebrewResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @janhq/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of @janhq/core for CVE-2024-36857. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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 to detect CVE-2024-36857
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2024-36857 -u https://target- Template
- Jan v0.4.12 'readFileSync' - Path Traversal
- Severity
- high
- Impact
- Unauthenticated attackers can read arbitrary files from the system via path traversal in the readFileSync interface.
- Remediation
- Update Jan to a version later than v0.4.12 that patches the path traversal vulnerability.
Template by ProjectDiscovery nuclei-templates (Yusuf Amr), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2024-36857 in your dependencies?
Find it across npm, including transitive dependencies.