OpenText Vibe · CSRF Vulnerability
Affects vibeSource GCVE Database
Not known to be exploited · CVSS 2.3 Low.
Data as of 16 Nov 2026, 16:51 UTC
Thin evidence
One scorer or none| CNA (OpenText) | CVSS 4.0 | 2.3 |
|---|
- Affects
- OpenText Vibe up to 4.0.8.7
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Opentextopentext/vibepkg:rpm/opentext/vibeOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, users should avoid using vulnerable versions in insecure environments and consider additional protective measures such as enforcing HTTPS to prevent token exposure over insecure connections.
Description
A CSRF vulnerability exists in OpenText Vibe versions up to 4.0.8.7 that could expose the CSRF token over insecure connections or make it accessible to JavaScript, reducing the effectiveness of protections against forged requests. This vulnerability has a low severity rating and no known exploits in the wild. No official patch or remediation information is provided in the available data.