[kburger]

Snyk has created this PR to fix 4 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

• pom.xml

Vulnerabilities that will be fixed with an upgrade:

	Issue	Upgrade
	Directory Traversal SNYK-JAVA-CHQOSLOGBACK-19882330	ch.qos.logback:logback-classic: 1.6.1 -> 1.6.3 `` No Known Exploit
	Allocation of Resources Without Limits or Throttling SNYK-JAVA-COMFASTERXMLJACKSONCORE-19778370	com.fasterxml.jackson.core:jackson-databind: 2.22.1 -> 2.22.2 com.fasterxml.jackson.dataformat:jackson-dataformat-yaml: 2.22.1 -> 2.22.2 Major version upgrade No Path Found No Known Exploit
	Deserialization of Untrusted Data SNYK-JAVA-COMFASTERXMLJACKSONCORE-19496766	com.fasterxml.jackson.core:jackson-databind: 2.22.1 -> 2.22.2 com.fasterxml.jackson.dataformat:jackson-dataformat-yaml: 2.22.1 -> 2.22.2 Major version upgrade No Path Found Proof of Concept
	Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') SNYK-JAVA-COMFASTERXMLJACKSONCORE-19477042	com.fasterxml.jackson.core:jackson-databind: 2.22.1 -> 2.22.2 com.fasterxml.jackson.dataformat:jackson-dataformat-yaml: 2.22.1 -> 2.22.2 Major version upgrade No Path Found No Known Exploit

Breaking Change Risk

Notice: This assessment is enhanced by AI.

Vulnerabilities that could not be fixed

• Upgrade:
  • Could not upgrade org.eclipse.rdf4j:rdf4j-rio-turtle@5.3.1 to org.eclipse.rdf4j:rdf4j-rio-turtle@6.0.0; Reason could not apply upgrade, dependency is managed externally ; Location: provenance does not contain location
• Could not upgrade org.eclipse.rdf4j:rdf4j-repository-sail@5.3.1 to org.eclipse.rdf4j:rdf4j-repository-sail@6.0.0; Reason could not apply upgrade, dependency is managed externally ; Location: provenance does not contain location

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Directory Traversal
🦉 Deserialization of Untrusted Data
🦉 Allocation of Resources Without Limits or Throttling

[kburger]

The upgrade of org.eclipse.rdf4j from version 5.3.1 to 6.0.0 is a high-risk major update that introduces significant breaking changes requiring developer action. The other package upgrades are low-risk patch releases.

org.eclipse.rdf4j:rdf4j-rio-turtle & rdf4j-repository-sail (5.3.1 → 6.0.0)

This is a major release with several backward-incompatible changes. [5]

Key Breaking Changes:

• Java 25 Required: The minimum required Java version has been raised to 25. [1, 5]
• Jakarta Servlet Migration: The framework has migrated from javax.servlet to Jakarta Servlet APIs. Applications that embed RDF4J Server or Workbench, or supply custom servlet filters, must update javax.* imports to jakarta.* and ensure they are deployed on a compatible Jakarta runtime (e.g., Jetty 12, Tomcat 11). [1, 5]
• HTTP Client API Overhaul: The previous API exposing Apache HttpComponents 4 has been removed. Code that programmatically configures or supplies a custom HTTP client must be migrated to the new client-neutral API. [2, 3]
• API and Dependency Updates: The release includes support for RDF 1.2 and SPARQL 1.2, which may require API migration for code using older RDF-star types. [1] It also brings major updates to core dependencies like Spring 7, Lucene 10, and Jackson 3. [1]

Recommendation: Before merging, developers must verify the application's Java runtime is at least version 25, update code to use the Jakarta Servlet APIs, and refactor any custom HTTP client configurations to align with the new RDF4J 6.0.0 API.

Other Upgrades (Low Risk)

• com.fasterxml.jackson: The upgrades for jackson-databind and jackson-dataformat-yaml to version 2.22.2 are patch releases containing security and bug fixes with no documented breaking changes. [10]
• ch.qos.logback: The upgrade for logback-classic to 1.6.3 is a patch release that addresses a CVE and maintains backward compatibility. [8, 11]

Source: RDF4J 6.0.0 Release Notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[kburger]

✅ 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

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[qplevier]

bumped elsewhere