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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 6/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 2.0.3.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Read the original 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
Upgrade to a fixed version: 2.0.3.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- marketcalls OpenAlgo
From 1.0.0.29 · fixed in 2.0.3.1
Evidence 5
- Patch
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120250
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: github.com
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: github.com
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: github.com
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: cve.now feed data