External risk intelligence

Omnispace Agora Project Authentication Bypass via Password Hash Replay

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-63158

Omnispace Agora Project is a collaborative web application suite commonly deployed as an internet-facing portal for remote access and project management. As a web-based platform with authentication mechanisms, it is routinely exposed to the public internet in standard deployment patterns.

Authentication Bypass

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability exists in Omnispace Agora Project that could allow unauthorized access by bypassing authentication. This occurs when an attacker uses a stolen password hash to impersonate legitimate users, including administrators, by manipulating specific cookies.

  • Stolen password hashes grant unauthorized access.
  • Critical access risk to sensitive applications.
  • Confirm relevance and potential exposure.

Attack Path

How an attacker could exploit the issue

Attackers can bypass authentication by obtaining a user's bcrypt password hash. By treating this hash as a directly replayable credential in specific cookies, an attacker can impersonate any user, including administrators, to gain unauthorized access to the application.

  • Requires a stolen password hash.
  • Exploits cookie-based authentication.
  • Leads to unauthorized administrative access.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, attackers possessing a user's stored bcrypt password hash could bypass authentication to impersonate any user, including administrators, and gain unauthorized access to the application.

  • User account access at risk.
  • Stolen password hashes could be replayed.
  • Unauthorized application access is possible.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Omnispace Agora Project's authentication bypass vulnerability likely falls under the responsibility of application owners and platform teams. The first practical step is to inventory all instances of the affected technology, confirm their internet reachability and business criticality, and identify the specific application owner responsible for each. Once identified, remediation can be planned based on the assessed risk.

  • Application and platform teams own resolution.
  • Verify internet-facing instances and criticality.
  • Plan remediation with vendor coordination.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Omnispace Agora Project?

Omnispace Agora Project is a collaborative web application suite designed for project management and remote team coordination. It serves as a centralized portal where users share documents, manage tasks, and communicate. Because it is a web-based platform, organizations typically deploy it as an internet-facing application to ensure team members can access project resources from any location.

What does CVE-2026-63158 mean for authentication?

This vulnerability is classified as CWE-836, which involves the use of non-cryptographic or improperly handled authentication tokens. In this case, the application's legacy cookie mechanism incorrectly treats a stored bcrypt password hash as a valid, replayable credential. Essentially, if an attacker obtains this hash, the system accepts it as a substitute for the actual password, allowing them to bypass the login process entirely.

How do attackers trigger this authentication bypass?

An attacker triggers this by injecting a stolen bcrypt password hash into the AGORAP_LOG or AGORAP_PASS cookies within their browser. The vulnerability does not require the attacker to know the user's plaintext password; possession of the hash is sufficient. This bug is only triggered when these specific legacy cookies are utilized; if the system is configured to ignore these cookies or utilize a different authentication flow, this specific bypass path is not available.

Why should I care about this if my Agora instance is internal?

Halo Surface Signal indicates that Omnispace Agora Project is frequently deployed as an internet-facing portal. If your instance is accessible from the public internet, the risk is higher because remote attackers can attempt to inject these cookies without needing internal network access. Even for internal instances, this remains a critical risk if an attacker has already gained a foothold within your network or accessed stored user data.

What should I do to respond to this vulnerability?

Your first step is to perform an inventory of all Omnispace Agora Project installations within your environment. Identify which instances are reachable from the internet and determine their business criticality. Once mapped, coordinate with your application owners to prioritize these systems for updates or remediation. Confirming the location and owner of each instance is essential to planning an effective security response.

References