← Back
CVE-2026-71497
medium
CVSS 4.7
Cross-Site Scripting (XSS) in org.jsoup:jsoup (CVE-2026-71497)
Summary
cross-site scripting in org.jsoup:jsoup (CVE-2026-71497). Risk of unauthorized operations or information disclosure. Exploitable via ``Safelist``. Mitigation: upgrade to `1.23.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-71497** has been found in org.jsoup:jsoup.
Attackers can target a specific entry point like ``Safelist`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.7/10.
What to do: upgrade org.jsoup:jsoup to **1.23.1** or later.
If unsure, ask your IT team or search "org.jsoup:jsoup CVE-2026-71497" on the vendor's site.
CVE-2026-71497 (org.jsoup:jsoup) — CWE-79 / CVSS v3 4.7
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `Safelist` / `style`
Patched: `1.23.1` — apply immediately
Workaround: Until upgrading, do not permit raw-text elements in custom Safelists used to clean untrusted HTML.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in org.jsoup:jsoup. Attackers reach the vulnerable code path via ``Safelist`` without authentication.
📍 Affected scope
org.jsoup:jsoup — . Attack surface: `Safelist` / `style`.
🔥 Severity
Severity: Medium (CVSS 4.7/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.23.1**.
🛡️ Workaround
Workaround: Until upgrading, do not permit raw-text elements in custom Safelists used to clean untrusted HTML.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.jsoup:jsoup' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.jsoup:jsoup' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.jsoup:jsoup` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Until upgrading, do not permit raw-text elements in custom Safelists used to clean untrusted HTML.パッチが適用されるまでの応急処置として、Until upgrading, do not permit raw-text elements in custom Safelists used to clean untrusted HTML. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade org.jsoup:jsoup to 1.23.1ステージング環境で 1.23.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.jsoup:jsoup
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.23.1"}]}]