Skip to main content

OpenAlgo CVE-2026-120250

| EUVDEUVD-2026-114747 MEDIUM
Improper Certificate Validation (CWE-295)
2026-11-01 VulnCheck GHSA-pxjx-g7g8-jwq6
6.0
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain network position on SMTP path
  2. Delivery
    Present forged TLS certificate to OpenAlgo
  3. Exploit
    Handshake succeeds (hostname/cert checks disabled)
  4. Execution
    Capture SMTP credentials and relayed mail
  5. Impact
    Harvest password-reset links for account takeover

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V12 - Secure Communication Certificate validation
Exploitation Conditions

The weakness is in OpenAlgo's shipped code, not a user toggle: utils/email_utils.py and utils/email_debug.py set check_hostname=False and verify_mode=CERT_NONE on both the STARTTLS and SMTPS (implicit TLS) paths, so every affected instance (1.0.0.29 up to before 2.0.3.1) that sends mail is exposed without any special configuration. Exploitation requires (1) the instance to have SMTP email configured and in use (e.g. for password-reset mail), and (2) the attacker to hold an active man-in-the-middle position on the network path between OpenAlgo and its mail server to present a forged certificate during the handshake - this positioning requirement (AV:A, AC:H, AT:P) is the primary limiting factor on real-world exploitation. No authentication or user interaction on the victim side is needed (PR:N/UI:N). Per the patch notes, a mail host entered as an IP address fails verification by design after the fix.

Impact

This is a medium-severity confidentiality issue (vendor CVSS 4.0 base 6.0), and the real-world signals are consistent with that rather than with an urgent emergency. The vulnerability requires an attacker who is already network-positioned between OpenAlgo and its mail server, reflected in AV:A (adjacent), AC:H (high complexity), and AT:P (a specific attack requirement - the attacker must intercept and present a forged certificate during the TLS handshake), with no privileges or user interaction needed (PR:N/UI:N). Impact is confidentiality-only (VC:H, VI:N/VA:N): interception of SMTP credentials and subsequent mail including password-reset links. No EPSS score is provided in the input, so exploitation probability cannot be quantified here. There is no CISA KEV listing and no public exploit or PoC reference in the supplied data, so exploitation status is 'no public exploit identified at time of analysis.' The vuln.today decision label is 'this_month,' which aligns with the moderate score and the need for a privileged network position - a genuine fix-this-cycle item but not a drop-everything emergency. The main caveat is that CVSS 4.0 was authored with AV:A, whereas a man-in-the-middle on an SMTP path can in some deployments be reachable remotely; defenders whose mail traffic crosses untrusted networks should treat the attack surface as broader than 'adjacent' implies.

Exploit ScenarioDerived

An attacker able to intercept traffic on the network path between an OpenAlgo instance and its configured SMTP server (for example on a shared or untrusted network segment) presents a forged TLS certificate. Because the affected code sets check_hostname=False and CERT_NONE for both STARTTLS and SMTPS, OpenAlgo completes the handshake without validating the certificate and sends its SMTP username and password, allowing the attacker to capture credentials and all subsequent mail, including password-reset links. No public exploit code is identified in the available data, and the attack requires the attacker to be positioned on the connection path (AC:H/AT:P).

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 01, 2026

OpenAlgo 1.0.0.29 up to but excluding 2.0.3.1 ships SMTP client code that switches off TLS certificate and hostname verification, so a network-positioned attacker who can intercept the path between OpenAlgo and its configured mail server can present a forged certificate, terminate the TLS session, and read the SMTP username and password along with every subsequent message - including password-reset links. The weakness is in the shipped code itself (utils/email_utils.py and utils/email_debug.py) and applies to both STARTTLS and implicit SMTPS paths, so any affected instance that sends mail is exposed without special configuration. Exploitation still requires the attacker to hold an active man-in-the-middle position (AV:A, AC:H, AT:P), which is the main limiter; no public exploit has been identified at time of analysis and no active exploitation is confirmed, making this a medium-severity confidentiality issue suited to scheduled, this-month remediation rather than emergency response.

RemediationAI

Vendor-released patch: upgrade to OpenAlgo 2.0.3.1 or later, which routes every SMTP TLS path through mail_tls_context() in utils/email_utils.py with hostname checking and certificate verification enabled, and stops enabling smtplib debug output that leaks the AUTH line (patch commit af5d5f2cc564ee31cdd1159bc147a9b03cc713ac; release notes at https://github.com/marketcalls/openalgo/blob/main/docs/releases/version-2.0.3.1-released.md). Apply the upgrade during this month's scheduled maintenance rather than as an emergency change; the issue is rated medium severity with a prerequisite man-in-the-middle position. After upgrading, confirm the SMTP host is configured as a DNS name that matches the mail server's certificate - the vendor's fix states that a host entered as an IP address fails verification by design - and verify that debug-level SMTP output is not enabled in utils/email_debug.py, since that path prints the SMTP password to stderr. No alternate mitigation is documented by the vendor; the advisory notes that the certificate check cannot be selectively re-enabled while running an affected build.

Affected VersionsENISA

OpenAlgo 1.0.0.29 <2.0.3.1

Affected Packages

euvd openalgo fix: 2.0.3.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is CWE-295 (improper certificate validation) in OpenAlgo's Python email helpers. The SMTP client builds its SSL context with check_hostname=False and verify_mode=ssl.CERT_NONE, disabling both chain-of-trust validation and hostname matching on the STARTTLS upgrade path and on the implicit-TLS (SMTPS) path. Because smtplib delegates the handshake to that context, any certificate - including a self-signed one naming an unrelated host - completes the handshake, after which AUTH credentials are sent in the clear to the impersonated server. The same code base also enabled smtplib's set_debuglevel(), which prints the AUTH line carrying the password to stderr. The upstream fix centralizes context creation in a mail_tls_context() helper in utils/email_utils.py, adds a specification note in docs/design/47-smtp-config/README.md, and adds test/test_smtp_certificate_verification.py, which stands up a local mail server with a forged self-signed certificate and asserts that no credentials or message bodies reach it while a trusted certificate still logs in successfully. Per the vendor notes, a mail host configured as a bare IP address fails verification by design once the fix is applied. Affected CPE: cpe:2.3:a:marketcalls:openalgo:*:*:*:*:*:*:*:*.

Know when Openalgo gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 6.0 MEDIUM
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
vuln.today AI 5.3 MEDIUM

Requires an adjacent man-in-the-middle position and a forged-certificate handshake (AV:A, AC:H), needs no privileges or interaction (PR:N/UI:N), and leaks credentials and mail for confidentiality-only impact (C:H, I:N/A:N).

3.1 AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:A/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Adjacent
Attack Complexity
High
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.1%
Top 99% exploitable
Prevalence
Low
niche algorithmic-trading platform, limited enterprise deployment footprint
Social Media
2
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Controlled
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy