jsoup may not sanitize code injection XSS attempts if SafeList.preserveRelativeLinks is enabled

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2022-36033: 1.64% estimated exploitation activity in the next 30 days; percentile 76.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

jsoup may incorrectly sanitize HTML including javascript: URL expressions, which could allow cross-site scripting (XSS) attacks when a reader subsequently clicks that link. If the non-default SafeList.preserveRelativeLinks option is enabled, HTML including javascript: URLs that have been crafted with control characters will not be sanitized. If the site that this HTML is published on does not set a Content Security Policy, an XSS attack is then possible. Impact Sites that accept input HTML from users and use jsoup to sanitize that HTML, may be vulnerable to cross-site scripting (XSS) attacks, if they have enabled SafeList.preserveRelativeLinks and do not set an appropriate Content Security Policy. Patches This issue is patched in jsoup 1.15.3. Users should upgrade to this version. Additionally, as the unsanitized input may have been persisted, old content should be cleaned again using the updated version. Workarounds To remediate this issue without immediately upgrading: - disable…

Published by the source

1 Sep 2022, 22:14 UTC

Last modified by the source

2 Feb 2023, 05:04 UTC

Source last checked

26 Oct 2026, 16:07 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gp7f-rwcx-9369

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-36033

Advisory: jsoup may not sanitize code injection XSS attempts if SafeList.preserveRelativeLinks is enabled
IDs: CVE-2022-36033, GHSA-gp7f-rwcx-9369
Record: https://patchnext.com/advisories/cve-2022-36033 (revision 1, source checked 26 Oct 2026, 16:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.jsoup:jsoup 1.15.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jsoup:jsoup: affected < 1.15.3; fixed in 1.15.3

## Suggested inspection (read-only)
- Maven org.jsoup:jsoup: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.jsoup:jsoup.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gp7f-rwcx-9369 (GitHub-reviewed advisory GHSA-gp7f-rwcx-9369 lists affected ranges: Maven org.jsoup:jsoup >=0 <1.15.3)

Commands are suggestions: review each one before running it.