dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-15579

CRITICAL · 9.5 CVSS v4.0 Published 2026-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Deserialization of Untrusted Data vulnerability in OpenText™ Directory Services allows Object Injection.  The vulnerability could lead to remote code execution, denial of service, or privilege escalation. This issue affects Directory Services: before 24.4.16, from 25.1 before 25.1.9, from 25.2 before 25.2.9, from 25.3 before 25.3.8, from 25.4 before 25.4.5, from 26.1 before 26.1.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a deserialization vulnerability (CWE-502) in OpenText Directory Services where untrusted data is deserialized without proper validation, allowing attackers to inject malicious objects. This can lead to remote code execution, denial of service, or privilege escalation. The critical CVSS score of 9.5 reflects the severe potential impact of RCE.

MitigationUpgrade OpenText Directory Services to version 24.4.16, 25.1.9, 25.2.9, 25.3.8, 25.4.5, or 26.1.2 or later. Apply the appropriate patched version based on your current release branch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
Authentication
Y
User interaction
None
Scope
P

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:Y/R:U/V:C/RE:M/U:Red

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate OpenText Directory Services installation
    Search for the OpenText Directory Services installation directory (commonly under /opt/opentext or C:\Program Files\OpenText on Windows). Look for version information in product-specific files or use any available version command-line tool.
    Affected if The installed version is 24.4.x before 24.4.16, 25.1.x before 25.1.9, 25.2.x before 25.2.9, 25.3.x before 25.3.8, 25.4.x before 25.4.5, or 26.1.x before 26.1.2, or if the version cannot be determined.
  2. Identify the running Directory Services process
    On the system running OpenText Directory Services, check for running Java processes associated with the product, or query the service manager for Directory Services entries.
    Affected if The Directory Services process is running and the version matches the affected ranges above.
  3. Check network exposure of Directory Services ports
    Review firewall rules and network configuration to determine which network interfaces and ports the Directory Services component is bound to, particularly any LDAP or Java RMI ports used for directory lookups.
    Affected if The service is accessible on network interfaces reachable from untrusted networks.
  4. Review logs for deserialization-related activity
    Examine Directory Services logs for entries indicating failed deserialization attempts, unusual object instantiation, or class loading errors, particularly from external sources.
    Affected if Log entries show deserialization errors or suspicious object loading from untrusted sources.

A user is affected if OpenText Directory Services is installed and running with a version prior to the patched releases (24.4.16, 25.1.9, 25.2.9, 25.3.8, 25.4.5, or 26.1.2) and the service is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OpenText Directory Services to version 24.4.16, 25.1.9, 25.2.9, 25.3.8, 25.4.5, or 26.1.2 or later. Apply the appropriate patched version based on your current release branch.

Recommended fix High confidence

Upgrade to the latest available version in your current branch: 24.4.16+, 25.1.9+, 25.2.9+, 25.3.8+, 25.4.5+, or 26.1.2+ (or the most recent overall release)

  1. Identify your current OpenText Directory Services version from the administration console or system information
  2. Determine which version branch you are currently running (24.4.x, 25.1.x, 25.2.x, 25.3.x, 25.4.x, or 26.1.x)
  3. Download the appropriate fixed version from OpenText support portal (support.opentext.com) - for 24.4.x use 24.4.16+, for 25.1.x use 25.1.9+, for 25.2.x use 25.2.9+, for 25.3.x use 25.3.8+, for 25.4.x use 25.4.5+, for 26.1.x use 26.1.2+
  4. Review upgrade documentation and release notes for your specific version path
  5. Create a backup of your current Directory Services configuration and data
  6. Stop the Directory Services instance before upgrading
  7. Install the fixed version following standard OpenText upgrade procedures
  8. Start the upgraded Directory Services instance
Caveat Review release notes for your specific upgrade path; major version jumps (e.g., 24.4 to 25.x) may have breaking changes in configuration or functionality

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15579 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15579 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data