# CVE-2026-87897: CVE-2026-87897

Status: published. Published: 2026-10-27. Updated: 2026-11-04.

A SSRF vulnerability found that enables access to internal Chrome Devtools Protocol APIs that can leak the JWT authentication token for another user. A low privileged attacker could continually exploit this vulnerability to leak the JWT authentication token for another user when they start a recording, which then enables the attacker read/write access to the victim's Whiteboard.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Nextcloud / whiteboard: ≥ 1.0.0; < 1.0.0 (affected, semver). Source: CNA: hackerone

## Severity and prioritization

- CVSS 3.0: 4.6 (medium); CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N; source: CNA: hackerone

- CISA KEV: No listing in collected sources

- EPSS: 0.20% as of 2026-11-04; percentile 10.35%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: CWE-918

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://hackerone.com/reports/3576823 (CNA: hackerone)

## Provenance

- CNA: hackerone: https://www.cve.org/CVERecord?id=CVE-2026-87897; retrieved 2026-11-04; source updated 2026-11-04

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-87897; retrieved 2026-11-04; source updated Not reported

Revision: 29ac0656ce04e0235b84f28e420db02ef59edc11fa3f3d7e7c56208215c0fa5b

Canonical: https://y2.dev/cve/CVE-2026-87897

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.