Skip to main content
CVE-2026-63170VulnerabilityPublished

Omnispace Agora Project through 26.10.0 contains a predictable token generation vulnerability that allows

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-63170· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium.

Data as of 13 Nov 2026, 19:48 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.3
CNA (VulnCheck)CVSS 3.13.7
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
OmnispaceAgora ProjectAffected
  • <=26.10.0
Fixed in–
GitHubAgora Projectpkg:github/Agora ProjectOther threatsAffected
  • <=26.10.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since this is a token generation weakness, mitigation would require changing the token generation mechanism to use unpredictable or cryptographically secure values. Until a fix is available, restricting access to shared calendar feeds or disabling token-based sharing may reduce risk.

Description

Omnispace Agora Project versions through 26.10.0 have a vulnerability in token generation where the shared-calendar iCal share token can be predicted and forged by unauthenticated attackers. This is due to the token being derived from predictable fields such as object creation time, which is disclosed in the calendar metadata. Exploiting this allows unauthorized reading of shared calendar iCal feeds.

References

Community reviews

Loading reviews…