Skip to main content
Menu
CVEs

CVE

Omnispace Agora Project predictable token flaw leaks calendar events in DisplayIcal

CVE-2026-63151EUVD-2026-125582

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

8.7HighCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

Do first: Workaround: The checked facts name no workaround. Until a fix is available, limiting or disabling the DisplayIcal feature is the only option the sources imply, but they do not state this as a vendor recommendation.

Published
Last modified
Reference
Last checked
0.42% · 37th percentile
31/100
Unclear
None on Exploit-DB, Metasploit or GitHub

Summary

Omnispace Agora Project is affected by a predictable token flaw that lets anyone on the network, without logging in, compute valid tokens and read the private calendar events of any user. The attacker does this by forging a token derived from small, guessable numbers and requesting the calendar export endpoint.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

Omnispace Agora Project through 26.10.0 contains a predictable token generation vulnerability that allows unauthenticated attackers to access private calendar data by exploiting a missing dateCrea value that causes the md5Id token to collapse to md5(calendarId.userId), both small enumerable integers. Attackers can compute valid tokens and request the misc&action=DisplayIcal endpoint with a forged md5Id to read any user's private calendar events without authentication.

Who should check

Teams running Omnispace or self-hosted Agora Project up to and including 26.10.0 that use shared or personal calendars.

“Omnispace Agora Project through 26.10.0 contains a predictable token generation vulnerability”

vulncheck.com

cve.now Index

31cve.now Index 31 of 100 · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 76 if added to CISA KEV
  • Would score about 71 if CISA's SSVC rates exploitation active
  • Would score about 36 if advisories confirm default setups are exposed

What to do

  • Workaround: The checked facts name no workaround. Until a fix is available, limiting or disabling the DisplayIcal feature is the only option the sources imply, but they do not state this as a vendor recommendation.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-63151 (Omnispace Agora Project 26.10.0 Predictable Token Information Disclosure via DisplayIcal), 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-63151 (entry last updated 2026-11-13):
Affected:
- Omnispace Agora Project: through 26.10.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Agora Project version 26.10.0 or earlier (through 26.10.0). (source: https://www.vulncheck.com/advisories/omnispace-agora-project-predictable-token-information-disclosure-via-displayical)
- A missing dateCrea value, which makes the md5Id token collapse to md5(calendarId.userId). (source: https://www.vulncheck.com/advisories/omnispace-agora-project-predictable-token-information-disclosure-via-displayical)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-63151 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63151 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://www.akailabs.fr/blog/multiple-vulnerabilities-in-agora-project-26-5-2#cve-2026-63151-personal-calendars-zero-entropy-md5id-share-token-allows-unauthen
- https://www.agora-project.net/
- https://www.vulncheck.com/advisories/omnispace-agora-project-predictable-token-information-disclosure-via-displayical
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-63151
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-63151"}.

Public exploit activity

100%0Nov 13Nov 17
  • EPSS: 0.42%

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Record last updated

Affected versions

  • Omnispace Agora Project

    through 26.10.0

Evidence 5

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Link
  2. Link
  3. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-63151

Is CVE-2026-63151 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: cve.now feed data

What does this mean?

The DisplayIcal feature generates a predictable token (md5Id) when a dateCrea value is missing, so it collapses to md5(calendarId.userId). An attacker who can compute that value can forge a valid token and read another user's private calendar events without logging in.Source: vulncheck.com

Which versions are affected by CVE-2026-63151?

Agora Project: through 26.10.0.Source: cve.now feed data

Am I affected, and how do I check?

Omnispace Agora Project through version 26.10.0 is listed as affected, and the flaw needs a missing dateCrea value to trigger. Check the installed Agora Project version to see whether it falls within that range.Source: vulncheck.com

How do I fix CVE-2026-63151?

No fixed version or vendor patch identifier is listed in the checked facts, so no upgrade target can be named from these sources. Check the vendor's advisory for an update.Source: vulncheck.com

What if there's no patch?

The checked facts name no workaround. Until a fix is available, limiting or disabling the DisplayIcal feature is the only option the sources imply, but they do not state this as a vendor recommendation.Source: vulncheck.com