Skip to content

fix: bump jsoup pin to 1.23.2 to resolve Snyk resource allocation vulnerability - #313

Merged
reeshika-h merged 1 commit into
masterfrom
fix/jsoup-cve-2026-75140
Aug 27, 2026
Merged

fix: bump jsoup pin to 1.23.2 to resolve Snyk resource allocation vulnerability#313
reeshika-h merged 1 commit into
masterfrom
fix/jsoup-cve-2026-75140

Conversation

@reeshika-h

Copy link
Copy Markdown
Contributor

Problem

jsoup is pulled in transitively via com.contentstack.sdk:utils@1.5.1 and is flagged by Snyk (SNYK-JAVA-ORGJSOUP-19233597, CVE-2026-75140) for unbounded resource allocation in XmlTreeBuilder's namespace scope tracking. No published utils release contains the fix yet.

Fix

  • Bump the existing dependencyManagement jsoup pin 1.23.1 → 1.23.2 (this repo already overrides jsoup transitively for a prior XSS CVE, same mechanism).
  • Bump SDK version 2.8.1 → 2.8.2 and add the CHANGELOG entry.
  • This pin can be dropped once contentstack-utils-java releases a version built against jsoup 1.23.2 and contentstack-utils-version is bumped to match.
  • Snyk's advisory has no fixed version on record yet, so the scan may still flag this even though the vulnerable code path is patched.

…nerability

jsoup is pulled in transitively via com.contentstack.sdk:utils and is
flagged by Snyk (CVE-2026-75140) for unbounded memory growth in
XmlTreeBuilder's namespace scope tracking. Fixed upstream in 1.23.2 via
a rewritten NamespaceBindings scope tracker. Bump the dependencyManagement
pin following the existing pattern used for other contentstack-utils
transitive deps.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@reeshika-h
reeshika-h requested a review from a team as a code owner August 26, 2026 09:16
@reeshika-h reeshika-h self-assigned this Aug 26, 2026
@snyk-io

snyk-io Bot commented Aug 26, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@github-actions

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 1 25 ✅ Passed
🟡 Medium Severity 0 0 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 1
  • Medium without fixes: 0
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

@reeshika-h
reeshika-h merged commit 2f878ec into master Aug 27, 2026
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants