CVE
Open Text Connected MX root privilege escalation in agent update process
- Exploited
- No known exploitation
- Fix
- Fixed in 25.2
- Who is exposed
- Specific setups only
Do first: Upgrade to a fixed version: 25.2.
Summary
Privilege escalation in OpenText Connected MX lets a local user with low privileges on a macOS endpoint gain root access through the Connected MX Agent update process. The attack requires access to the machine itself and no action from another user.
Original description
Improper Verification of Cryptographic Signature vulnerability in OpenText™ Connected MX allows Privilege Escalation. The vulnerability could allow a local, low-privileged user of a macOS endpoint to gain root privileges through the Connected MX Agent update process. This issue affects Connected MX macOS Agent: before 25.2.
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 8.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Upgrade to a fixed version: 25.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2025-2235 (Privilege escalation in OpenText™ Connected MX), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2025-2235 (entry last updated 2026-11-18):
Affected:
- Open Text Connected MX: fixed in 25.2
Fixed versions: 25.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2025-2235 is not listed as of cve.now's last read.
This KEV status is for CVE-2025-2235 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://my.opentext.com/support/article/9394749
- https://www.cve.org/CVERecord?id=CVE-2025-2235
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2025-2235
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2025-2235"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Open Text Connected MX
fixed in 25.2
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2025-2235 |
| Record | NVD · CVE-2025-2235 |
| Other links 1 | |
| Advisory | my.opentext.com · support/article/9394749 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2025-2235
Is CVE-2025-2235 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
Which versions are affected by CVE-2025-2235?
Connected MX: before 25.2.Source: cve.now feed data
How do I fix CVE-2025-2235?
Upgrade to a fixed version: 25.2. The vendor's advisory also recommends 25.2 or later or later.Source: cve.now feed data, cve.org