OPENTEXT VIBE · CVE-2026-3860 · Vendor
NO FIX YET
OpenText Vibe versions up to and including 4.0.8.7 can expose its anti-forgery token over an insecure connection or make it readable by JavaScript. That weakens protection against forged requests, so an attacker may be able to trigger actions as a logged-in user.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that run OpenText Vibe at version 4.0.8.7 or earlier. The sources do not say which deployment settings make it exploitable, so unknown.
Who cares opentext-vibe, self-hosted
No fix yet, per the sources.
CSRF vulnerability in OpenText Vibe versions <= 4.0.8.7 could expose the token over an insecure connection or make it accessible to JavaScript, weakening protection against forged requests.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/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:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.