Quick answers
- Is CVE-2026-120250 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-120250 being exploited in the wild.
- How severe is CVE-2026-120250?
- Medium severity, with a CVSS score of 5.3, published 1 November 2026.
- Which products and versions are affected?
- Marketcalls OpenAlgo 1.0.0.29 through 2.0.3.0.
- Is there a fix for CVE-2026-120250?
- Yes: fixed in 2.0.3.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-120250 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-120250?
- Check whether you run Marketcalls OpenAlgo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.0.3.1
Technical details
OpenAlgo versions 1.0.0.29 through 2.0.3.0 disable TLS hostname and certificate validation in utils/email_utils.py and utils/email_debug.py for STARTTLS and SMTPS connections. A network-positioned attacker can present a forged certificate to intercept SMTP authentication credentials and all subsequent email traffic, including sensitive password-reset communications. The fix is available in version 2.0.3.1 and later.
Affected products
- marketcalls OpenAlgo 1.0.0.29 through 2.0.3.0
Timeline
- 2026-11-01: disclosed