Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-4249

Denial of Service via Malicious JSON Payloads in Throttling Events in Multiple WSO2 Products Causing Persistent Service Disruption

Description

The throttling event handling mechanism in multiple WSO2 products accepts user-supplied JSON payloads without sufficient validation of their structure and content. This allows an unauthenticated remote attacker to inject malicious JSON data that can lead to a persistent denial of service condition. Successful exploitation of this vulnerability can disrupt the API Gateway, preventing legitimate API traffic from being processed and impacting complete service availability. The denial of service is persistent, requiring manual intervention to restore normal operations.

Timeline

  1. ID reserved

    By WSO2

  2. · 4 months later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-4249, by who scored it
Scored byCVSSScoreVector
WSO2CNA (assigner)3.1High8.6CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
NVDNVD · Analyzed3.1High8.6CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.56% · top 53% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • WSO2 · WSO2 Universal Gateway

    • affected 4.5.0 – < 4.5.0.54
    • affected 4.6.0 – < 4.6.0.18
    • affected 4.7.0 – < 4.7.0.2
  • WSO2 · WSO2 Traffic Manager

    • affected 4.5.0 – < 4.5.0.53
    • affected 4.6.0 – < 4.6.0.18
    • affected 4.7.0 – < 4.7.0.2
  • WSO2 · WSO2 API Control Plane

    • affected 4.5.0 – < 4.5.0.55
    • affected 4.6.0 – < 4.6.0.19
    • affected 4.7.0 – < 4.7.0.2
  • WSO2 · WSO2 API Manager

    • unknown < 3.2.0
    • affected 3.2.0 – < 3.2.0.470
    • affected 3.2.1 – < 3.2.1.89
    • affected 4.0.0 – < 4.0.0.390
    • affected 4.1.0 – < 4.1.0.254
    • affected 4.2.0 – < 4.2.0.194
    • affected 4.3.0 – < 4.3.0.105
    • affected 4.4.0 – < 4.4.0.69
    • affected 4.5.0 – < 4.5.0.54
    • affected 4.6.0 – < 4.6.0.18
    • affected 4.7.0 – < 4.7.0.2

What to do

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

References

References1

Sources

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

Badge for a README or a ticket

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

Record last updated .