Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-94456 – Predictable OAuth Tokens & Credentials via Weak PRNG – Postiz < 2.24.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-94456 is a critical (CVSS 9.1) weakness in Postiz, an open-source social media scheduling and management platform, in which security-sensitive credentials are generated using Math.random() instead of a cryptographically secure random source. Because OAuth access tokens, authorization codes, client secrets, organization API keys, and PKCE verifiers are all produced by the same insecure generator, an attacker who can observe enough of its output can reconstruct the underlying PRNG state and predict other credentials it produces.

Technical details

  • Root cause: Postiz relies on JavaScript’s non-cryptographic Math.random() (V8’s deterministic xorshift128+ PRNG) to generate OAuth access tokens, authorization codes, client secrets, organization API keys, and PKCE verifiers.
  • Trigger condition: An unauthenticated OAuth dynamic client registration endpoint returns freshly generated client credentials to any caller, giving an attacker a stream of consecutive PRNG outputs.
  • Attack vector: Network-based, no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N). By collecting outputs from the exposed endpoint, an attacker can mathematically recover the PRNG’s internal state.
  • Impact: Once the PRNG state is recovered, an attacker can deterministically derive past and future credential values generated by the same instance — enabling prediction/forgery of OAuth access tokens, authorization codes, client secrets, API keys, and PKCE verifiers belonging to other users and organizations, potentially leading to account and organization takeover. The vulnerability affects confidentiality and integrity but not availability.

Affected software

  • GitroomHQ Postiz (postiz-app): all versions prior to 2.24.0 (releases from 2.4.0 through 2.23.0 are confirmed affected).

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Postiz to version 2.24.0 or later, which addresses this issue.
  • If immediate patching is not possible:
    • Restrict or disable public access to the OAuth dynamic client registration endpoint at the network or reverse-proxy layer until the upgrade can be applied.
    • Rotate all existing OAuth tokens, authorization codes, client secrets, API keys, and PKCE verifiers after upgrading, since values generated prior to the patch may have been predictable.
    • Monitor for anomalous OAuth client registrations or token usage originating from unexpected sources.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge