How severe is CVE-2023-6836?

CVE-2023-6836 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

How do I fix CVE-2023-6836?

Update org.wso2.carbon.commons:org.wso2.carbon.ntask.core to 4.7.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-6836 is resolved across your whole dependency graph.

How do I detect CVE-2023-6836 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wso2.carbon.commons:org.wso2.carbon.ntask.core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-6836 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2023-6836 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-6836 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-6836?

CVE-2023-6836 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-6836?

CVE-2023-6836 is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-6836 published, and has it been updated?

CVE-2023-6836 was published on December 15, 2023 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2023-6836 — org.wso2.carbon.ntask.core

HIGHFix: wso2/carbon-analytics-common@9478336

CVE-2023-6836 is a high-severity (CVSS 7.5) XML External Entity (XXE) vulnerability in org.wso2.carbon.commons:org.wso2.carbon.ntask.core. A fix is available for org.wso2.carbon.commons:org.wso2.carbon.ntask.core — see the affected versions and patch details below.

WSO2 products vulnerable to XML External Entity attack

Also known asGHSA-cr8h-fr86-8vfv

Published

Dec 15, 2023

Updated

Oct 24, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

6 pkgs affected

☕org.wso2.carbon.commons:org.wso2.carbon.ntask.core☕org.wso2.am:wso2am☕org.wso2.carbon.registry:org.wso2.carbon.registry.extensions☕org.wso2.carbon.event-processing:org.wso2.carbon.event.processor.core☕org.wso2.carbon.analytics-common:org.wso2.carbon.event.input.adapter.core☕org.wso2.carbon.governance:org.wso2.carbon.governance.common

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Multiple WSO2 products have been identified as vulnerable due to an XML External Entity (XXE) attack abuses a widely available but rarely used feature of XML parsers to access sensitive information.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.wso2.carbon.commons:org.wso2.carbon.ntask.core`	all versions	4.7.24`org.wso2.carbon.commons:org.wso2.carbon.ntask.core:4.7.24`
☕Maven	`org.wso2.am:wso2am`	all versions	4.0.0-beta`org.wso2.am:wso2am:4.0.0-beta`
☕Maven	`org.wso2.carbon.registry:org.wso2.carbon.registry.extensions`	all versions	4.7.31`org.wso2.carbon.registry:org.wso2.carbon.registry.extensions:4.7.31`
☕Maven	`org.wso2.carbon.event-processing:org.wso2.carbon.event.processor.core`	all versions	2.2.12`org.wso2.carbon.event-processing:org.wso2.carbon.event.processor.core:2.2.12`
☕Maven	`org.wso2.carbon.analytics-common:org.wso2.carbon.event.input.adapter.core`	all versions	5.2.23`org.wso2.carbon.analytics-common:org.wso2.carbon.event.input.adapter.core:5.2.23`
☕Maven	`org.wso2.carbon.governance:org.wso2.carbon.governance.common`	all versions	4.8.13`org.wso2.carbon.governance:org.wso2.carbon.governance.common:4.8.13`

Affected Products

7 products · 14 configurations

Application

api managerwso2

≤ 3.0.0

range

Application

api manager analyticswso2

2 versions

2.2.02.5.0

Application

api microgatewaywso2

1 version

2.2.0

Application

enterprise integratorwso2

≤ 6.6.0

range

Application

identity serverwso2

4 versions

5.4.05.4.15.5.05.6.0

Application

identity server as key managerwso2

4 versions

5.0.05.6.05.7.05.9.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wso2.carbon.commons:org.wso2.carbon.ntask.core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.wso2.carbon.commons:org.wso2.carbon.ntask.core to 4.7.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-6836 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Multiple WSO2 products have been identified as vulnerable due to an XML External Entity (XXE) attack abuses a widely available but rarely used feature of XML parsers to access sensitive information.

O3 Security · Impact-Aware SCA

Is CVE-2023-6836 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-611XML External Entity (XXE)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

carbon-analytics-common

3.9/10

Maintained5/10

Code-Review4/10

Branch-ProtectionN/A

Assessed Oct 19, 2026

Timeline

Disclosed

Dec 15, 2023

Last updated

Oct 24, 2026

Identifiers

CVE-2023-6836

GHSA-cr8h-fr86-8vfv

References

Advisorysecurity.docs.wso2.com · WSO2 2020 0716 Advisorynvd.nist.gov · CVE 2023 6836 Webgithub.com · 9478336859306d3ea13b25cb386f29c183707fde Webgithub.com · a08a587e3dd5146121a7b47a0fdd06ddbcd903f4 Webgithub.com · e9953afd46a45f704de341a081f710cbdfa3f975 Webgithub.com · ad36968d5a11d4fc35fa5cc4e8b5ae9a04e5bb4c Webgithub.com · 738b2a0b3e5f118527da236467ed72d9fd9ce40e Webgithub.com · 96e8f5d6566d57bbbb8d4257f6f55057a79d00b5 Websecurity.docs.wso2.com · WSO2 2020 0716

Related vulnerabilities

This CVE is high severity; 8 of 8 other CVEs with CWE-611 are rated as high or higher (top: critical).

CVE-2026-108358CVE-2026-108357CVE-2026-61586CVE-2026-61741CVE-2026-61570CVE-2026-55848CVE-2026-54079CVE-2026-54078Browse all CWE-611

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2023-6836 — org.wso2.carbon.ntask.core

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2023-6836 in your dependencies?