Skip to content
Web

CVE-2026-33229

8.6
High
EPSS 0.54%Patch availableApr 9, 2026

XWiki: script-right bypass enables Python code execution, compromising the instance.

common questions

Is CVE-2026-33229 being exploited?

Not confirmed. CVE-2026-33229 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.54% probability of exploitation in the next 30 days.

How severe is CVE-2026-33229?

CVE-2026-33229 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-33229?

Yes. A fix has been recorded for CVE-2026-33229. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-33229 affect?

CVE-2026-33229 affects XWiki Platform (versions <17.4.8, <17.10.1). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-33229?

Upgrade to 17.4.8 or 17.10.1+

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
XWiki Platform (versions <17.4.8, <17.10.1)
impact

Auth user with script rights can bypass sandbox, execute Python code, gaining full control of the XWiki instance.

action required

Patch when possible

affected versions
xwiki xwiki-platform
  • affected>= 17.0.0-rc-1 and < 17.4.8
  • affected>= 17.5.0-rc-1 and < 17.10.1
org.xwiki.platform xwiki-platform-legacy-oldcore
  • affected>= 17.0.0-rc-1 and < 17.4.8
  • affected>= 17.5.0-rc-1 and < 17.10.1
org.xwiki.platform xwiki-platform-oldcore
  • affected>= 17.0.0-rc-1 and < 17.4.8
  • affected>= 17.5.0-rc-1 and < 17.10.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free