# CVE-2026-63149: Omnispace Agora Project < 26.10.0 Predictable Default Password via uniqid()


- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-g4xx-c33q-625w

## What is CVE-2026-63149?

CVE-2026-63149 is a critical vulnerability in Omnispace Agora Project, published on 13 Oct 2026. 

### Official description

Omnispace Agora Project before 26.10.0 contains an insecure randomness vulnerability that allows attackers to predict temporary or default account passwords generated by Txt::defaultPassword() using PHP's uniqid() function based on server time in microseconds. Attackers who observe or approximate the account creation time can compute the predictable password and take over the account before the legitimate user logs in.

Weakness: CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2026-63149?


## How do I fix CVE-2026-63149?

No fix has been published for CVE-2026-63149 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63149 being exploited?

There is no known exploitation of CVE-2026-63149 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63149 and fix it if it is affected.

What it is: CVE-2026-63149 is a critical vulnerability in Omnispace Agora Project, published on 13 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-63149 in the wild and no public exploit code.

Affected product: Omnispace Agora Project. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63149/ (Markdown: https://insights.sbomify.com/CVE-2026-63149/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63149
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63149
- OSV: https://osv.dev/vulnerability/CVE-2026-63149

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63149/
Summaries are generated and may contain mistakes; the official description above is the record.