mJS
Cesanta
- Product type
- Software application
- Catalog vulnerabilities
- 85
Severity across 1 analyzed records
- Products & ServicesProducts & Services
- SolutionsSolutions
- PricingPricing
- CompanyCompany
- ResourcesResources
en
en
Severity across 1 analyzed records
Verify to analyze this security profile
As of 09/14/2026, within CyStack's analyzed data, mJS has 1 security vulnerability published in the last 90 days. Of these, 0 are rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of mJS and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-86716Cesanta mJS mjs_tok.c skip_spaces_and_comments heap-based overflow | Exploitation statusPublic exploit | FixNot confirmed | Published09/08/2026 | SeverityMedium |
CVE-2024-35385 | Exploitation statusPublic exploit | FixNot confirmed | Published05/21/2024 | SeverityMedium |
CVE-2024-35384 | Exploitation statusPublic exploit | FixNot confirmed | Published05/21/2024 | SeverityMedium |
CVE-2024-35386 | Exploitation statusNot known exploited | FixNot confirmed | Published05/21/2024 | SeverityHigh |
CVE-2023-49552 | Exploitation statusPublic exploit | FixNot confirmed | Published01/02/2024 | SeverityHigh |
CVE-2023-49550 | Exploitation statusPublic exploit | FixNot confirmed | Published01/02/2024 | SeverityHigh |
CVE-2023-49549 | Exploitation statusPublic exploit | FixNot confirmed | Published01/02/2024 | SeverityHigh |
CVE-2023-49553 | Exploitation statusPublic exploit | FixNot confirmed | Published01/02/2024 | SeverityHigh |
CVE-2023-49551 | Exploitation statusPublic exploit | FixNot confirmed | Published01/02/2024 | SeverityHigh |
CVE-2023-50044 | Exploitation statusNot confirmed | FixNot confirmed | Published12/20/2023 | SeverityUnknown |
CVE-2023-43338 | Exploitation statusPublic exploit | FixNot confirmed | Published09/22/2023 | SeverityUnknown |
CVE-2023-30088 | Exploitation statusPublic exploit | FixNot confirmed | Published05/09/2023 | SeverityMedium |
CVE-2023-30087 | Exploitation statusNot known exploited | FixNot confirmed | Published05/09/2023 | SeverityMedium |
CVE-2023-29570 | Exploitation statusPublic exploit | FixNot confirmed | Published04/24/2023 | SeverityMedium |
CVE-2023-29569 | Exploitation statusPublic exploit | FixNot confirmed | Published04/14/2023 | SeverityMedium |
CVE-2023-29571 | Exploitation statusPublic exploit | FixNot confirmed | Published04/12/2023 | SeverityMedium |
CVE-2021-36535 | Exploitation statusPublic exploit | FixNot confirmed | Published02/03/2023 | SeverityMedium |
CVE-2021-33443 | Exploitation statusNot confirmed | FixNot confirmed | Published07/26/2022 | SeverityUnknown |
CVE-2021-33444 | Exploitation statusNot confirmed | FixNot confirmed | Published07/26/2022 | SeverityUnknown |
CVE-2021-33445 | Exploitation statusNot confirmed | FixNot confirmed | Published07/26/2022 | SeverityUnknown |
CVE-2021-33446 | Exploitation statusNot confirmed | FixNot confirmed | Published07/26/2022 | SeverityUnknown |
CVE-2021-33447 | Exploitation statusNot confirmed | FixNot confirmed | Published07/26/2022 | SeverityUnknown |
CVE-2021-33448 | Exploitation statusNot confirmed | FixNot confirmed | Published07/26/2022 | SeverityUnknown |
CVE-2021-33449 | Exploitation statusNot confirmed | FixNot confirmed | Published07/26/2022 | SeverityUnknown |
CVE-2021-33442 | Exploitation statusNot confirmed | FixNot confirmed | Published07/26/2022 | SeverityUnknown |
CVE-2021-33441 | Exploitation statusNot confirmed | FixNot confirmed | Published07/26/2022 | SeverityUnknown |
CVE-2021-33440 | Exploitation statusNot confirmed | FixNot confirmed | Published07/26/2022 | SeverityUnknown |
CVE-2021-33439 | Exploitation statusNot confirmed | FixNot confirmed | Published07/26/2022 | SeverityUnknown |
CVE-2021-33438 | Exploitation statusNot confirmed | FixNot confirmed | Published07/26/2022 | SeverityUnknown |
CVE-2021-33437 | Exploitation statusNot confirmed | FixNot confirmed | Published07/26/2022 | SeverityUnknown |
CVE-2021-46556 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46554 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46553 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46550 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46549 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46548 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46547 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46546 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46545 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46544 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46543 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46542 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46541 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46540 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46539 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46538 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46537 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46535 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46534 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46532 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46531 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46530 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46528 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46529 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46527 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46526 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46525 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46524 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46523 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46522 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46521 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46520 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46519 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46518 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46517 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46516 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46515 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46513 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46514 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46512 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46510 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46511 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46509 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2021-46508 | Exploitation statusNot confirmed | FixNot confirmed | Published01/27/2022 | SeverityUnknown |
CVE-2020-36375 | Exploitation statusNot confirmed | FixNot confirmed | Published05/28/2021 | SeverityUnknown |
CVE-2020-36373 | Exploitation statusNot confirmed | FixNot confirmed | Published05/28/2021 | SeverityUnknown |
CVE-2020-36374 | Exploitation statusNot confirmed | FixNot confirmed | Published05/28/2021 | SeverityUnknown |
CVE-2020-36369 | Exploitation statusNot confirmed | FixNot confirmed | Published05/28/2021 | SeverityUnknown |
CVE-2020-36372 | Exploitation statusNot confirmed | FixNot confirmed | Published05/28/2021 | SeverityUnknown |
CVE-2020-36367 | Exploitation statusNot confirmed | FixNot confirmed | Published05/28/2021 | SeverityUnknown |
CVE-2020-36368 | Exploitation statusNot confirmed | FixNot confirmed | Published05/28/2021 | SeverityUnknown |
CVE-2020-36370 | Exploitation statusNot confirmed | FixNot confirmed | Published05/28/2021 | SeverityUnknown |
CVE-2020-18392 | Exploitation statusNot confirmed | FixNot confirmed | Published05/28/2021 | SeverityUnknown |
CVE-2020-36371 | Exploitation statusNot confirmed | FixNot confirmed | Published05/28/2021 | SeverityUnknown |
CVE-2020-36366 | Exploitation statusNot confirmed | FixNot confirmed | Published05/28/2021 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan
