Release notes

GraphDB release notes provide information about the features and improvements in each release, as well as various bug fixes. GraphDB’s versioning scheme is based on semantic versioning. The full version is composed of three components:

major.minor.patch

e.g., 10.8.0 where the major version is 10, the minor version is 8 and the patch version is 0.

Occasional versions may include a modifier after a hyphen, e.g., 10.8.1-RC1 to signal additional information, e.g., a test release (TR1, TR2 and so on), a release candidate (RC1, RC2 and so on), a milestone release (M1, M2 and so on), or other relevant information.

Note

Releases with the same major and minor versions do not contain any new features. Releases with different patch versions contain fixes for bugs discovered since the previous minor version. New or significantly changed features are released with a higher major or minor version.

GraphDB 10 includes the following components with their version numbers:

  • RDF4J

  • GraphDB Connectors

  • GraphDB Workbench

Their versions use the same semantic versioning scheme as the whole product, and their values are provided only as a reference.

GraphDB 11.0.2

Released: 7 July 2025

Component versions

RDF4J

Connectors

Workbench

5.1.2

16.3.3

3.0.2

Important

GraphDB 11.0.2 fixes major issues causing cluster node locks after leader elections, incomplete rollbacks when entity pool IDs were exhausted, and repository initialization failures during backup restores. It also delivers numerous improvements and fixes for GraphQL.

This release addresses two security issues related to file read and file upload handling for authenticated users, ensuring safer operation in secured environments.

We recommend everyone to upgrade.

GraphDB Engine and Cluster

New features and improvements

  • GDB-12245 Enable socket keep alive probes on HTTP client used for federated services

  • GDB-10256 Improve validation and error handling for the entity-index-size repository configuration

Bug fixing

  • GDB-12424 Issues with creating a cluster and processing queries in transactions when using cluster external proxy

  • GDB-12382 Cannot create a cluster with OpenID/OAuth security enabled

  • GDB-12371 Value of graphdb_slow_queries_count in Prometheus statistics is never incremented

  • GDB-12335 Misleading wording on deprecated configuration properties in log

  • GDB-12313 Invalid repository ID used in SPARQL internal federation shows as “lock cannot be acquired error”

  • GDB-12248 Repository cannot initialize with “Not a built-in ruleset: ‘null’” error

  • GDB-12234 File upload vulnerability resulting in uploads to arbitrary locations on disk

  • GDB-12208 Incomplete rollback of entity pool when the entity pool IDs are exhausted

  • GDB-12206 Cluster node lock after leader election during import

  • GDB-12167 GraphQL: Suboptimal execution plan for query with connectors

  • GDB-12114 Arbitrary file read vulnerability to any authenticated user

  • GDB-12106 GraphQL endpoint from SHACL generation error: “langAppendDefaultNameFetch” parameter is set to true, but the checkbox in the endpoint configuration is indicating false

  • GDB-12105 GraphQL endpoint generation errors mention roles with the CUSTOM_ prefix

  • GDB-12095 GraphQL RBAC ctx.roles produces invalid SPARQL query in some cases

  • GDB-12091 GraphQL endpoint generation: generating an endpoint with RBAC with invalid filters duplicates the error message in the validation

  • GDB-12073 GraphQL endpoint generation: SPARQL fragments are sometimes generated with a newline

  • GDB-12052 GraphQL endpoint generation: Misleading error message on missing repository in request

  • GDB-12049 GraphQL error “Could not execute query due to: Found multiple values for a property defined as single-valued”

  • GDB-11998 Cluster breaks when trying to restore a backup with repositories that cannot be initialized

  • GDB-11948 Cannot restore from S3 with “Connection pool shut down” error

  • GDB-11936 Handle Java warning “A restricted method in java.lang.foreign.Linker has been called”

  • GDB-11935 Wrong evaluation of queries with VALUES in OPTIONAL that introduce a variable used in a sub-SELECT projection

  • GDB-11931 GraphQL SOML schema with an invalid pattern does not trigger an error when uploaded

  • GDB-11496 GraphQL nested create fails with error “It is required to use ‘patch’ or ‘where’ to update …”

GraphDB Workbench

New features and improvements

  • GDB-7219 Enable editing of autocomplete label IRIs in Autocomplete view

Bug fixing

  • GDB-12372 Link to ChatGPT Retrieval Connector does not work in TTYG create agent view when GraphDB is behind a reverse proxy with a context path different from /

  • GDB-12327 Users with read-only access cannot copy SPARQL queries from SPARQL template and visual graph config

  • GDB-12319 Class hierarchy show/hide prefixes icon does not work

  • GDB-12146 Welcome page shows namespaces error for users with only GraphQL access

  • GDB-12134 Unable to save a new query under a previously used name

  • GDB-12123 REST API documentation broken for cloud backup, cloud restore, and restore

  • GDB-11243 Cannot enable Free Access unless a page refresh is done

  • GDB-7797 Normalize spaces in the names of saved Visual graphs to avoid visually indistinguishable names

  • GDB-7796 Keyboard navigation while creating a new saved Visual graph leaks background HTML elements

GraphDB Connectors and Plugins

New features and improvements

  • GDB-12210 Improve error handling for failed JSTL transformations in annotation service integration in Text Mining plugin

Bug fixing

  • GDB-12176 Transaction history plugin fails with “History transaction ID already used” for any new transaction IDs

GraphDB distributions and deployment

New features and improvements

  • GDB-12323 Update various libraries to address known vulnerabilities

Bug fixing

  • GDB-12179 Misleading missing license log messages when starting the cluster proxy

GraphDB 11.0.1

Released: 7 May 2025

Component versions

RDF4J

Connectors

Workbench

5.1.2

16.3.2

3.0.1

Important

GraphDB 11.0.1 fixes a critical file upload vulnerability allowing uploads to arbitrary disk locations, and major issues with GraphQL and cluster creation. In addition, the release includes various other fixes and improvements for stability and performance.

We recommend everyone to upgrade.

GraphDB Engine and Cluster

New features and improvements

  • GDB-12153 Improve the messages when a GraphQL feature requires a GraphQL extended license

  • GDB-12112 Use the X-Forwarded-Host and X-Forwarded-Proto headers to construct repository URLs in the response of the repository list API

Bug fixing

  • GDB-12167 Suboptimal execution plan for GraphQL query with connectors

  • GDB-12163 Incorrect repository size reported within the context of an active transaction

  • GDB-12143 SPARQL queries with UNION combining VALUES and BIND return incomplete results

  • GDB-12131 Editing a GraphQL endpoint adds a duplicate unionOf in schema and makes it unusable

  • GDB-12113 File upload vulnerability resulting in uploads to arbitrary locations on disk

  • GDB-12111 Unexpected error on login if the provided username or password is empty

  • GDB-12037 Empty result on listing repository statements with a specific predicate in cluster

  • GDB-12011 Cluster creation could fail if shutdown of repositories takes longer than 30 seconds

  • GDB-11946 Incorrect handling of several GraphQL configuration properties: graphdb.graphql.query.cartesianProductCheck, graphdb.graphql.mutation.nestedCreate, graphdb.graphql.query.maxObjectsReturned, and graphdb.graphql.sparql.federated.services.<service_id>

  • GDB-11714 GraphQL mutation with nested create fails for types with access: none

GraphDB Workbench

New features and improvements

  • GDB-11996 Improve UI spacing in GraphQL endpoint management wizard

  • GDB-11944 Download GraphQL queries in Query monitoring as .json instead of .rq

  • GDB-11923 Improve messaging on hitting file size limits when importing a GraphQL schema

Bug fixing

  • GDB-12097 GraphQL pages show error when legacy remote locations are attached via Workbench

  • GDB-12078 Editing an existing text snippet in the Import view and re-importing it does not reflect the edited data

  • GDB-12050 Incorrect suggested values for GraphQL endpoints in REST API documentation

  • GDB-12006 GraphiQL pop-up menu’s text is much too large

  • GDB-11916 Unable to import .gz files through Workbench on MacOS

  • GDB-11287 Entity pool metrics not shown correctly in System monitoring

GraphDB distributions and deployment

New features and improvements

  • GDB-12158 Update various libraries to address known vulnerabilities

GraphDB 11.0.0

Released: 8 April 2025

Component versions

RDF4J

Connectors

Workbench

5.1.2

16.3.1

3.0.0

Important

GraphDB 11 introduces significant enhancements aimed at improving usability, performance, and security. The release features native GraphQL integration, optimized repository management for handling many repositories efficiently, major updates to key libraries including RDF4J 5.x, Spring Framework 6.x, and a higher Java version requirement (Java 21).

Licensing changes in GraphDB 11 require manual license installation for GraphDB Free, replacing the previously built-in license, and introduce additional feature restrictions compared to the commercial GraphDB editions.

Additionally, GraphDB 11 includes numerous bug fixes and smaller improvements, enhancing overall product stability and user experience. For users needing immediate bug fixes without upgrading to version 11, GraphDB 10.8.5 was recently released and remains available.

The development of the features in this release was partially funded by the EnrichMyData (GA nu: 101070284) Horizon Europe eu-flag research project.

GraphQL

GraphDB 11 introduces built-in support for GraphQL, streamlining RDF data access and management directly within the product. This enhancement replaces the previous standalone Semantic Objects solution, bringing key features like high availability, robust security, and multi-tenancy into a unified, easy-to-use GraphQL interface.

Designed with developers in mind, the new GraphQL integration enables intuitive, efficient interaction with RDF data without the complexities of SPARQL queries or RDF handling. Developers can now:

  • Effortlessly retrieve data in familiar JSON and JSON-LD formats, optimizing integration with JavaScript-based web applications.

  • Precisely define queries to target specific data subsets, improving retrieval efficiency and minimizing overhead.

  • Enforce closed-world validations, maintaining high data integrity and consistency.

  • Manage granular access permissions to ensure secure and controlled data interactions.

  • Flexibly utilize multiple contexts within a single dataset, supporting diverse application requirements without redundant data management.

  • Leverage internal federation capabilities for seamless integration of data across multiple repositories.

  • Explore intuitive data models through built-in GraphQL introspection, simplifying data discovery and application development.

This upgrade empowers developers to quickly build sophisticated, dynamic web applications, leveraging GraphDB’s comprehensive data capabilities with the ease and familiarity of GraphQL.

Working with a large number of repositories

GraphDB 11 enhances the repository management capabilities, significantly optimizing heap memory usage to efficiently support operation with a large number of repositories on a single instance. This update addresses the challenge of managing many repositories simultaneously by implementing a caching system at the repository manager level with an LRU (Least Recently Used) eviction policy. This policy dynamically manages the number of active repositories, reducing system stress and enhancing performance for actively used repositories.

Key improvements include:

  • Configurable maximum number of active repositories managed through an efficient LRU cache

  • Consistent updates and seamless evictions for inactive repositories

  • User-friendly error messages for scenarios exceeding cache limits

  • Option to enable or disable the caching feature

These advancements particularly benefit DevOps and managed service providers by significantly lowering hardware requirements and enabling large-scale repository management scenarios without sacrificing performance or consistency.

Major library upgrades and Java requirements

GraphDB 11 continues our commitment to staying at the forefront of modern technologies, featuring significant upgrades to core components. We have updated RDF4J to version 5.x, Spring Framework to version 6.x, and raised the minimum required Java version to 21. These updates ensure enhanced security, compatibility, and optimal performance.

Key improvements include:

  • Advanced SHACL capabilities: Enhanced SHACL validation and reasoning, leveraging powerful new features provided by RDF4J 5.x, enabling more expressive and performant validation.

  • Robust security enhancements: Benefit from Spring Framework 6.x’s latest security improvements, safeguarding your deployments with updated protection against vulnerabilities.

  • Performance optimization: Enjoy general performance improvements across the board, resulting from optimizations in RDF4J, Spring, and the modern capabilities of Java 21.

By adopting the latest versions of these foundational technologies, GraphDB 11 delivers a robust, secure, and efficient platform for your semantic technology applications.

Licensing changes

In GraphDB 11, the following licensing and feature changes affect GraphDB Free:

  • License requirement: The built-in license for GraphDB Free has been removed. Users upgrading to GraphDB Free 11 must request a free license from the Ontotext website and manually install it before use.

  • Repository limit: GraphDB Free now supports up to 5 repositories.

  • Authentication and Authorization: LDAP, OpenID/OAuth, Kerberos, and X.509 authentication and authorization methods are no longer available in GraphDB Free.

  • Entity ID restriction: Support for 40-bit entity IDs has been removed.

All these features remain available in GraphDB Enterprise and GraphDB Standard.

GraphDB Engine and Cluster

New features and improvements

  • GDB-11768 As an admin, I need to map custom roles in OAuth tokens without the CUSTOM_ prefix

  • GDB-11355 Support for apostrophe in SPARQL prefixedName (PN_LOCAL)

  • GDB-11232 As a user, I want to limit the number of active repositories in a GraphDB instance

  • GDB-10073 As a user, I want a more easy-to-understand version of the default.min.distinct.threshold system property

  • GDB-9845 Add ability to retrieve roles from different LDAP subtrees

  • GDB-9544 Introduce GraphQL interface in GraphDB

  • GDB-8983 Support for renaming a repository in cluster

  • GDB-5545 Support pairwise constraints in SHACL

Bug fixing

  • GDB-12046 Removal of explicit statements from graph may not work in cluster

  • GDB-11769 Roles mapped from OAuth tokens aren’t normalized to upper case

  • GDB-11667 TTYG explain response uses the query method’s default values instead of those from the agent configuration

  • GDB-11645 Unhandled errors during TTYG chat processing may leave a chat in an unusable state

  • GDB-11556 TTYG agent instructions are unnecessarily updated on every question after the data in the repository changes

  • GDB-11313 Accessing a remote location that is a follower node does not route specific requests to the leader

  • GDB-8557 Improve error handling when a SHACL SPARQLConstraint is not properly defined

GraphDB Workbench

New features and improvements

  • GDB-11693 Improve repository info popup usability

  • GDB-11245 Reintroduce entity-index-size property configuration for repositories in GraphDB Workbench

  • GDB-11270 Enable browser autocomplete for adding/replacing cluster nodes

  • GDB-10914 Handle new line in Visual Graph’s node basics in advanced graph configuration

  • GDB-6965 Improve usability of Graphs Overview view when there are thousands of named graphs

Bug fixing

  • GDB-11795 Free access user can not accept cookie policy due to undefined user

  • GDB-11416 The JSON-LD Context field cannot be set back to an empty value in the Import view

  • GDB-11292 Hovering over nodes in Visual Graph View causes overflow of long type names

  • GDB-11281 Workbench shows the edit/delete actions for saved queries shared by other users

  • GDB-10979 ACL view in the Workbench erroneously describes an old implementation of ACLs

  • GDB-10900 Broken global notification area in Workbench when the repository is named “repository”

GraphDB Connectors and Plugins

New features and improvements

  • GDB-11438 Make the Lucene connector max clause count configurable via a property

GraphDB distributions and deployment

New features and improvements

  • GDB-11926 Update various libraries to address known vulnerabilities

  • GDB-11865 Remove the built-in GraphDB Free license from the distribution

  • GDB-11475 Upgrade to Spring Framework 6.x

  • GDB-9418 Upgrade to RDF4J 5.x