Content spoofing via manipulated cached text
Published Feb 19, 2026 · Updated Feb 19, 2026
Content spoofing in OpenText Directory Services 20.4.1 through 25.2 allows remote attackers to inject text that misleads users. The vendor identifies cache poisoning as the means of changing displayed text but has not disclosed the affected request, cache, or rendering locus. Exploitation requires network access without privileges and passive user exposure; the reported consequence is altered UI information, not data disclosure or service interruption.
Summary
What happened
Content spoofing in OpenText Directory Services 20.4.1 through 25.2 allows remote attackers to inject text that misleads users. The vendor identifies cache poisoning as the means of changing displayed text but has not disclosed the affected request, cache, or rendering locus. Exploitation requires network access without privileges and passive user exposure; the reported consequence is altered UI information, not data disclosure or service interruption.
The record
- CVE
- CVE-2026-1658
- Published
- Feb 19, 2026
- Updated
- Feb 19, 2026
- Vendor
- OpenText
- Product
- OpenText Directory Services
- Classifications
- CWE-451, CAPEC-141, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2026CVE publishedPublication date reported by the CVE source.
- Feb 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=20.4.1 <=25.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo