# CVE-2026-94456: Weak cryptography in postiz-app

> Attackers can predict OAuth tokens and API keys by exploiting insecure random number generation, leading to unauthorized access to user accounts and data.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026

## What is CVE-2026-94456?

CVE-2026-94456 is a critical vulnerability in GitroomHQ postiz-app, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Postiz generates security-sensitive credentials using `Math.random()` instead of a cryptographically secure source. The same helper is used for OAuth access tokens, authorization codes, client secrets, organization API keys, and PKCE verifiers, meaning these credentials depend entirely on V8’s deterministic xorshift128+ PRNG state.

An unauthenticated OAuth dynamic client registration endpoint exposes freshly generated client credentials, giving attackers enough consecutive PRNG output to reconstruct that internal state. Once recovered, they can deterministically derive past and future values produced by the same generator, potentially compromising credentials belonging to other users and organizations.

Weakness: CWE-341 (Predictable from Observable State), CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)), CWE-330 (Use of Insufficiently Random Values)

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


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

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

## Is CVE-2026-94456 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94456 is a critical vulnerability in GitroomHQ postiz-app, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-94456 in the wild and no public exploit code.

Affected product: GitroomHQ postiz-app. 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-94456/ (Markdown: https://insights.sbomify.com/CVE-2026-94456/index.md)
```

## Sources

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

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