Information Disclosure in Multiple WSO2 Products Allows Exposure of Certificate File Paths

Description

The affected component fails to enforce expected validation constraints on the `content-type` header when processing certain requests. This allows an attacker to submit a crafted request with a manipulated `content-type` header. Successful exploitation can lead to the unintended exposure of the file paths for certificate files. This information disclosure could potentially be leveraged in subsequent attacks or compromise the confidentiality of the system.

Timeline

Scores

EPSS (exploitation in 30 days)

0.18% · top 92% of all CVEs (7 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: yes · Technical impact: partial

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

Weakness

• CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)All about CWE-200 and its CVEs

Affected products

• WSO2 · WSO2 Identity Server

  • unknown < 5.10.0
  • affected 5.10.0 – < 5.10.0.381
  • affected 5.11.0 – < 5.11.0.428
  • affected 6.0.0 – < 6.0.0.255
  • affected 6.1.0 – < 6.1.0.255
  • affected 7.0.0 – < 7.0.0.133
  • affected 7.1.0 – < 7.1.0.41
  • affected 7.2.0 – < 7.2.0.3

• WSO2 · WSO2 Open Banking IAM

  • unknown < 2.0.0
  • affected 2.0.0 – < 2.0.0.421

• WSO2 · WSO2 Identity Server as Key Manager

  • unknown < 5.10.0
  • affected 5.10.0 – < 5.10.0.372

• WSO2 · WSO2 Identity Server Keystore Rest API Commons

  • affected 1.0.82 – < 1.0.82.25
  • affected 1.0.190 – < 1.0.190.17
  • affected 1.2.3 – < 1.2.3.6
  • affected 1.2.23 – < 1.2.23.10
  • affected 1.2.176 – < 1.2.176.18
  • affected 1.3.83 – < 1.3.83.10
  • affected 1.3.213 – < 1.3.213.1
  • unaffected 1.3.221 – ≤ *

• WSO2 · WSO2 Identity Server Keystore Rest API V1

  • affected 1.0.82 – < 1.0.82.25
  • affected 1.0.190 – < 1.0.190.17
  • affected 1.2.3 – < 1.2.3.6
  • affected 1.2.23 – < 1.2.23.10
  • affected 1.2.176 – < 1.2.176.18
  • affected 1.3.83 – < 1.3.83.10
  • affected 1.3.213 – < 1.3.213.1
  • unaffected 1.3.221 – ≤ *

What to do

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

References (1)

• https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4751/ (opens in a new tab)vendor-advisory

Sources

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

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

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

Record last updated 2 Nov 2026, 19:20 UTC.