Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2026-3416

Predictable Pseudorandom Number Generation via Webhook HMAC Secret Generation in Multiple WSO2 Products Allows Forged Event Payloads

Medium5.9EPSS 0.36%
Published
Updated
Reserved
Assigned by
WSO2

Description

The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create shared secrets for Webhook HMAC validation. This PRNG lacks sufficient entropy for security-sensitive operations, allowing a sophisticated attacker to predict future secrets. This enables malicious actors to forge event payloads with valid HMAC signatures, bypassing the API Gateway's authenticity verification. Successful exploitation could allow an attacker to predict shared secrets used for Webhook HMAC validation and forge event payloads with valid signatures. This may enable bypassing API Gateway authenticity checks, leading to unauthorized event injection, data manipulation, or downstream system compromise.

Scores

CVSS scores of CVE-2026-3416, by who scored it
Scored byCVSSScoreVector
WSO2CNA (assigner)3.1Medium5.9CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVDNVD · Analyzed3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
0.36% · top 70% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.9.

Weakness

Affected products

  • WSO2 · WSO2 API Manager

    • unknown < 4.1.0
    • affected 4.1.0 – < 4.1.0.253
    • affected 4.2.0 – < 4.2.0.193
    • affected 4.3.0 – < 4.3.0.104
    • affected 4.4.0 – < 4.4.0.68
    • affected 4.5.0 – < 4.5.0.52

  • WSO2 · WSO2 API Control Plane

    • affected 4.5.0 – < 4.5.0.53

What to do

Solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5174/#solution

References (1)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-3416 badge
[![CVE-2026-3416](https://trackcve.app/badge/CVE-2026-3416.svg)](https://trackcve.app/cve/CVE-2026-3416)

Record last updated .