CVE
Omnispace Agora Project private message disclosure in mail handling
Agora Project through version 26.10.0 lets an authenticated user read the titles and bodies of other users' private mail. No fixed version is given in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Attacker must have an authenticated account on Agora Project up to 26.10.0. Affects Agora Project through version 26.10.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.37% · 30th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Omnispace Agora Project is affected by an insecure direct object reference flaw in its mail handling. A remote attacker with a low-privilege login can change the mail identifier in a request to read the title and body of other users' private messages.
Original description
Omnispace Agora Project through 26.10.0 contains an insecure direct object reference vulnerability that allows authenticated attackers to access another user's private mail by supplying a crafted reloadMailTypeId parameter to Ctrl::getCurObj() without a readRight() ownership check in CtrlMail.php. Attackers can manipulate the mail identifier value, such as reloadMailTypeId=mail-1, to retrieve the title and body of private messages belonging to other users, resulting in unauthorized disclosure of sensitive communications.
Who should check
Teams running Agora Project 26.10.0 or earlier, including Omnispace-hosted spaces that use the mail module, should check for this bug.
“Affecting Agora Project <= 26.10.0”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Attacker must have an authenticated account on Agora Project up to 26.10.0. Affects Agora Project through version 26.10.0.Workaround: The checked facts include no workaround or mitigation. Until a fix is confirmed, follow the vendor's guidance from its advisory.
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-63164 (Omnispace Agora Project 26.10.0 IDOR via reloadMailTypeId Parameter), 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-63164 (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):
- Attacker must have an authenticated account on Agora Project up to 26.10.0. (source: https://www.vulncheck.com/advisories/omnispace-agora-project-idor-via-reloadmailtypeid-parameter)
- Affects Agora Project through version 26.10.0. (source: https://www.vulncheck.com/advisories/omnispace-agora-project-idor-via-reloadmailtypeid-parameter)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-63164 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63164 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-63164-idor-in-reloadmailtypeid-allows-reading-and-exfiltration-of-other
- https://www.agora-project.net/
- https://www.vulncheck.com/advisories/omnispace-agora-project-idor-via-reloadmailtypeid-parameter
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-63164
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-63164"}.Public exploit activity
- EPSS: 0.37%
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Omnispace Agora Project
through 26.10.0
Evidence 5
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-63164
Is CVE-2026-63164 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?
An authenticated user can use the reloadMailTypeId parameter to access another user's private mail, reading the title and body of messages that belong to others.Source: vulncheck.com
Which versions are affected by CVE-2026-63164?
Agora Project: through 26.10.0.Source: cve.now feed data
Am I affected, and how do I check?
Agora Project versions through 26.10.0 are listed as affected, and the attacker needs an authenticated account on the product. To check a installation, look up its Agora Project version and compare it with 26.10.0.Source: vulncheck.com
How do I fix CVE-2026-63164?
The checked facts name no fixed version and no vendor patch identifiers, so no upgrade target can be given here. Check the vendor's advisory for a fix before relying on any version.Source: vulncheck.com
What if there's no patch?
The checked facts include no workaround or mitigation. Until a fix is confirmed, follow the vendor's guidance from its advisory.Source: vulncheck.com