CVE-2026-1658
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 · uneditedUser Interface (UI) Misrepresentation of Critical Information vulnerability in OpenText™ Directory Services allows Cache Poisoning. The vulnerability could be exploited by a bad actor to inject manipulated text into the OpenText application, potentially misleading users. This issue affects Directory Services: from 20.4.1 through 25.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 · moderate confidenceThis is a cache poisoning vulnerability in OpenText Directory Services where an attacker can inject manipulated text into the application's cache. When users request directory information, the poisoned cache serves the attacker-modified content, allowing misrepresentation of critical information to mislead users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 20.4.1, <= 25.2CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify OpenText Directory Services versionRun 'otds --version' or check the product information panel in the administration console. On Linux, also check '/opt/otds/version' or look in the installation directory for a version file.Affected if The installed version is 20.4.1 through 25.2 (inclusive)
-
Confirm Directory Services is runningCheck if the otds service is active: 'systemctl status otds' on Linux or check the Windows Services panel for 'OpenText Directory Services'.Affected if The service is running and the version falls in the affected range
-
Verify caching is enabledExamine the configuration file (typically 'otdss.conf' or 'cache-config.xml' in the configuration directory). Look for settings such as '<Cache enabled='true'>' or similar cache enablement flags.Affected if Caching is enabled and the version is in the affected range
-
Inspect cache storage locationLocate the cache directory (commonly under '/var/cache/otds' or the data directory). Examine cache files for unexpected content, altered entries, or files with recent modification timestamps that do not correspond to legitimate updates.Affected if Cache files contain unexpected or manipulated text content
-
Review access and cache logsExamine the Directory Services logs (typically in '/var/log/otds/') for unusual cache-related entries, repeated cache invalidation events, or requests that may indicate cache poisoning attempts.Affected if Logs show unusual cache behavior, repeated invalidations, or suspicious request patterns targeting cache endpoints
You are affected if OpenText Directory Services version 20.4.1 through 25.2 is installed with caching enabled, as this is the specific range where the cache poisoning vulnerability applies.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to a version beyond 25.2 when available, or implement cache validation/signing mechanisms to ensure cached content integrity. Review and flush existing caches to remove any potentially poisoned entries.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1658 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1658 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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