CVE-2026-94456

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 57% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

September 22, 2026

Last Modified

September 22, 2026

Advisory Details (4)

Auto-updated Sep 22, 2026
Patch available. Sources: github_release, github_commit.
generic

PSA-2026-TD98KY: Unauthenticated recovery of the Math.random() state behind OAuth tokens, authorization codes, client secrets and organization API keys · GAdvisory

https://gadvisory.org/advisories/PSA-2026-TD98KY
github_commit Patch Available

commit 9259cf2429e8 (gitroomhq/postiz-app)

Patch available: gitroomhq/postiz-app v2.24.0 (contains commit 9259cf2429e8)

https://github.com/gitroomhq/postiz-app/commit/9259cf2429e8cc0c88414e88d5e6c783d7ffba63
github_release Patch Available

Release v2.24.0 (gitroomhq/postiz-app)

Patch available: gitroomhq/postiz-app v2.24.0

https://github.com/gitroomhq/postiz-app/releases/tag/v2.24.0
generic

GitHub - gitroomhq/postiz-app: 📨 The ultimate agentic social media scheduling tool 🤖 · GitHub

https://github.com/gitroomhq/postiz-app

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-23 19:06 UTCEG score recompute
  2. 2026-09-23 17:54 UTCEPSS rescore
  3. 2026-09-22 19:38 UTCEG score recompute
  4. 2026-09-22 18:33 UTCEG score recompute
  5. 2026-09-22 17:36 UTCEG score recompute
  6. 2026-09-22 16:25 UTCEG score recompute
  7. 2026-09-22 16:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-94456?
CVE-2026-94456 is a critical vulnerability published on September 22, 2026. 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…
When was CVE-2026-94456 disclosed?
CVE-2026-94456 was first published in the National Vulnerability Database on September 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-94456 actively exploited?
CVE-2026-94456 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.7% of all scored CVEs.
What is the CVSS score of CVE-2026-94456?
CVE-2026-94456 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-94456?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-94456, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-94456

Explore →

Is Your Infrastructure Affected by CVE-2026-94456?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.