CVE-2025-70045: An issue pertaining to CWE-295: Improper Certificate Validation was discovered in jxcore jxm master
CVE-2025-70045 is a high-severity flaw (CVSS 7.4) affecting jxm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
An issue pertaining to CWE-295: Improper Certificate Validation was discovered in jxcore jxm master. The application disables TLS/SSL certificate validation by setting 'rejectUnauthorized': false in HTTPS request options when 'jx_obj.IsSecure' is true
Why this priority
- High severity
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 7.4 (High) |
| Attack vector | Network (remote) |
| Attack complexity | High |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.2% (top 92%) |
| CISA exploited list | No |
| Weakness | CWE-295 |
| Published | 2026-02-23 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-70045?
jxm: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2025-70045 being exploited?
CVE-2025-70045 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-70045 affect?
CVE-2025-70045 affects jxm. Severity is high (CVSS 7.4). An issue pertaining to CWE-295: Improper Certificate Validation was discovered in jxcore jxm master. The application disables TLS/SSL certificate validation by setting 'rejectUnauthorized': false in HTTPS request options when 'jx_obj.IsSecu
How urgent is CVE-2025-70045?
Priority 33/100. High severity; Remotely exploitable, no login, no user action