jsoup: Cleaner may expose markup with custom raw-text elements

Exploitation

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

CVSS

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

EPSS

• CVE-2026-71497: 0.30% estimated exploitation activity in the next 30 days; percentile 22.30 (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.

When a custom Safelist permits certain raw-text elements, jsoup may incorrectly sanitize malformed HTML containing a tag name that ends in a control character. The tag may acquire the parsing behavior of a different element, causing content that should remain text to be emitted as active markup after serialization and potentially allowing XSS. jsoup’s built-in Safelists are unaffected. Patches Upgrade to jsoup 1.23.1. Workarounds Until upgrading, do not permit raw-text elements in custom Safelists used to clean untrusted HTML. Additional security considerations This fix addresses malformed tag-name handling only. Permitting raw-text elements in a custom Safelist does not make their contents inherently safe. For example, applications that permit style must apply appropriate CSS safeguards separately, because jsoup does not parse or sanitize CSS.

Published by the source

6 Aug 2026, 21:09 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 16:54 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-pmhh-3w7g-xqp8

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-pmhh-3w7g-xqp8

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

# Patch Next advisory brief: CVE-2026-71497

Advisory: jsoup: Cleaner may expose markup with custom raw-text elements
IDs: CVE-2026-71497, GHSA-pmhh-3w7g-xqp8
Record: https://patchnext.com/advisories/cve-2026-71497 (revision 2, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.7)
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.23.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jsoup:jsoup: affected >= 1.14.3, < 1.23.1; fixed in 1.23.1

## 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://osv.dev/vulnerability/GHSA-pmhh-3w7g-xqp8 (OSV record GHSA-pmhh-3w7g-xqp8 lists affected ranges: Maven org.jsoup:jsoup >=1.14.3 <1.23.1 (fixed))
- Verified: https://github.com/advisories/GHSA-pmhh-3w7g-xqp8 (GitHub-reviewed advisory GHSA-pmhh-3w7g-xqp8 lists affected ranges: Maven org.jsoup:jsoup >=1.14.3 <1.23.1)

Commands are suggestions: review each one before running it.