jflyfox is a technology vendor producing software and infrastructure products. As a software provider, jflyfox's broad product portfolio across multiple domains—including operating systems, cloud infrastructure, enterprise applications, databases, networking, and security tools—creates a large attack surface. Additionally, long support cycles, widespread deployment, and continuous feature development contribute to the accumulation of discovered vulnerabilities over time. Major vendors typically report higher CVE counts not necessarily due to inferior security, but because of greater exposure to security research, responsible disclosure practices, and the sheer complexity of maintaining multiple product lines and legacy systems. Regular security assessments and patching of jflyfox's products are critical for organizations running their software in production environments.
SecUtils has indexed 51 known vulnerabilities from jflyfox. This includes 9 critical-severity issues and 30 high-severity issues that represent significant risk. These vulnerabilities affect 1 distinct product across jflyfox's portfolio, demonstrating the breadth of the vendor's product ecosystem and the importance of comprehensive patch management strategies. Disclosure dates span from 2021 through 2025, with recent active disclosure activity. Organizations deploying jflyfox products should maintain active vulnerability monitoring, prioritize critical patches, and implement compensating controls where patches cannot be applied immediately.
| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2020-19146 | 2021-09-15 | 2024-11-21 | 6.5 | 4.0 | Likely |
| CVE-2020-19147 | 2021-09-15 | 2024-11-21 | 6.5 | 4.0 | Likely |
| CVE-2020-19148 | 2021-09-15 | 2024-11-21 | 5.4 | 3.5 | Unknown |
| CVE-2020-19150 | 2021-09-15 | 2024-11-21 | 8.1 | 5.5 | Likely |
| CVE-2020-19151 | 2021-09-15 | 2024-11-21 | 8.8 | 6.5 | Likely |
| CVE-2020-19154 | 2021-09-15 | 2024-11-21 | 6.5 | 4.0 | Likely |
| CVE-2020-19155 | 2021-09-15 | 2024-11-21 | 8.8 | 6.5 | Likely |
| CVE-2021-40639 | 2021-09-15 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2021-37262 | 2021-12-16 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2021-46087 | 2022-01-25 | 2024-11-21 | 5.4 | 3.5 | Unknown |
| CVE-2022-27111 | 2022-04-11 | 2024-11-21 | 5.4 | 3.5 | Unknown |
| CVE-2022-28505 | 2022-05-03 | 2024-11-21 | 7.2 | 6.5 | Likely |
| CVE-2021-42242 | 2022-05-05 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2022-30500 | 2022-05-26 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2022-29648 | 2022-06-02 | 2024-11-21 | 5.4 | 3.5 | Unknown |
| CVE-2022-33113 | 2022-06-23 | 2024-11-21 | 5.4 | 3.5 | Unknown |
| CVE-2022-33114 | 2022-06-23 | 2024-11-21 | 7.2 | 6.5 | Likely |
| CVE-2022-34928 | 2022-08-03 | 2024-11-21 | 8.8 | - | - |
| CVE-2022-37199 | 2022-08-23 | 2024-11-21 | 9.8 | - | - |
| CVE-2022-37223 | 2022-08-23 | 2024-11-21 | 9.8 | - | - |
| CVE-2022-36527 | 2022-08-25 | 2024-11-21 | 5.4 | - | - |
| CVE-2022-38272 | 2022-09-09 | 2024-11-21 | 7.2 | - | - |
| CVE-2022-38273 | 2022-09-09 | 2024-11-21 | 7.2 | - | - |
| CVE-2022-38274 | 2022-09-09 | 2024-11-21 | 7.2 | - | - |
| CVE-2022-38275 | 2022-09-09 | 2024-11-21 | 7.2 | - | - |
| CVE-2022-38276 | 2022-09-09 | 2024-11-21 | 7.2 | - | - |
| CVE-2022-38277 | 2022-09-09 | 2024-11-21 | 7.2 | - | - |
| CVE-2022-38278 | 2022-09-09 | 2024-11-21 | 7.2 | - | - |
| CVE-2022-38279 | 2022-09-09 | 2024-11-21 | 7.2 | - | - |
| CVE-2022-38280 | 2022-09-09 | 2024-11-21 | 7.2 | - | - |
| CVE-2022-38281 | 2022-09-09 | 2024-11-21 | 7.2 | - | - |
| CVE-2022-38282 | 2022-09-09 | 2024-11-21 | 7.2 | - | - |
| CVE-2022-38283 | 2022-09-09 | 2024-11-21 | 7.2 | - | - |
| CVE-2022-38284 | 2022-09-09 | 2024-11-21 | 7.2 | - | - |
| CVE-2022-38285 | 2022-09-09 | 2024-11-21 | 7.2 | - | - |
| CVE-2022-38286 | 2022-09-09 | 2024-11-21 | 7.2 | - | - |
| CVE-2022-37207 | 2022-09-15 | 2024-11-21 | 8.8 | - | - |
| CVE-2022-37201 | 2022-09-15 | 2024-11-21 | 8.8 | - | - |
| CVE-2022-37203 | 2022-09-19 | 2024-11-21 | 9.8 | - | - |
| CVE-2022-37204 | 2022-09-20 | 2025-05-27 | 9.8 | - | - |
| CVE-2022-37205 | 2022-09-20 | 2025-05-28 | 8.8 | - | - |
| CVE-2022-37209 | 2022-09-27 | 2025-05-22 | 8.8 | - | - |
| CVE-2022-37208 | 2022-10-13 | 2025-05-15 | 8.8 | - | - |
| CVE-2022-37202 | 2022-10-26 | 2025-05-07 | 8.8 | - | - |
| CVE-2023-22975 | 2023-02-03 | 2024-11-21 | 6.1 | - | - |
| CVE-2023-24747 | 2023-04-05 | 2025-02-13 | 5.4 | - | - |
| CVE-2023-30349 | 2023-04-27 | 2025-01-31 | 9.8 | - | - |
| CVE-2023-34645 | 2023-06-16 | 2024-12-17 | 7.5 | - | - |
| CVE-2023-47503 | 2023-11-28 | 2024-11-21 | 9.8 | - | - |
| CVE-2024-53477 | 2024-12-02 | 2025-11-25 | 9.8 | - | - |
| CVE-2025-6105 | 2025-06-16 | 2026-04-29 | 4.3 | 5.0 | Likely |
SecUtils aggregates National Vulnerability Database (NVD) and MITRE records for jflyfox by normalizing vendor identifiers across diverse data sources, mapping vendor names to their associated product lines, and collecting all known vulnerabilities under a unified vendor context. For every CVE associated with jflyfox's products, we extract and structure Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) categories, CVSS severity metrics, and reference links to enable rapid vulnerability identification and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and vendor vulnerability tracking.