CIB seven 3.0.0 EE - Release Notes

Release Date: November 20, 2026

Highlights

  • Platform Jakarta EE 11 (EL 6.0, JAX-RS 4.0), Spring Boot 4.1 and Spring Framework 7 as the only Spring line, Java 17 as the minimum and Java 25 as a new supported version, with Java 25 Docker images
  • Jackson 3 The REST API, Spin JSON, the external task client, the Spring Boot starters, CIB seven Run and the webclient use Jackson 3; deprecated -jackson2 artifacts of Spin and the external task client remain for applications that cannot move yet
  • Legacy web applications removed The old Camunda Cockpit, Tasklist and Admin are no longer part of the distributions and the Spring Boot starters; use the CIB seven webclient
  • Ad hoc sub process The BPMN adHocSubProcess is supported from the model API to the REST API
  • Agentic ad hoc sub process (beta) An ad hoc sub process driven by the AI Agent Connector, which chooses the activities to start
  • AI Agent Connector Process variables and documents (PDF, images, text) as model input; the chat memory is kept per process instance (since 2.2.4)
  • MCP The REST API MCP Plugin ships with CIB seven Run and is switched on with MCP_ENABLED=true
  • External tasks Retry time cycle for external tasks and a fetched entry in the external task log
  • Modeler Diagrams and forms organized in folders and projects, process keys and form ids unique per folder (cibseven-modeler 1.3.0)
  • Webclient Frontend plugins, configurable deep links, a new header navigation, and UI permissions read from the user’s own authorizations
  • Notifications (EE exclusive) Administrators publish maintenance, incident or release notices as a banner for all users or selected groups
  • Project Members (EE exclusive) Modeler projects can be restricted to members with the roles Project Admin, Editor and Viewer
  • Form AI Agent (EE exclusive, beta) An AI panel in the form editor builds and changes forms from a description
  • Modeler EE (EE exclusive) Snapshots and comparison for forms, opt-in autosave, element template management, and a long-polling team chat that works in multi-pod deployments (cibseven-modeler-ee 1.3.0)
  • Database The webclient tables are an optional schema component (webclientExtensionsEnabled)
  • Direct Provider The Direct Provider of the webclient, which calls the engine in the same JVM instead of over the REST API, is no longer beta
  • Security Attachments and comments are protected by permission checks, JUEL scripts follow the restrictions of a customized expression manager, a hardening adds a deny list for expressions and scripts, active by default since 3.0.0, and opt-in allow lists for task types, script languages and connector endpoints, and the webclient connects only to configured engine REST servers (since 2.2.5); the task filter expression whitelist is enabled by default and the first-admin setup is offered only on an unconfigured engine (since 2.2.4); 219 CVEs and security advisories and Camunda Security Notice 157 resolved since 2.2.0 (15 Critical, 61 High, 82 Medium, 61 Low)

Breaking Changes

The update guide from 2.2 to 3.0 describes the migration steps.

  • Java 17 baseline. All CIB seven 3.x artifacts are compiled to Java 17 bytecode and no longer load on Java 11: the embedded engine, the standalone DMN engine, the external task client, the model APIs, Spin, Connect, Commons and the test libraries. Applications and external task workers must run on Java 17, 21 or 25. OSGi bundles require osgi.ee JavaSE 17. See Java 17 is required.
  • Jakarta EE only; the -jakarta artifacts are renamed. The javax (Java EE 8) variants are removed, and the unsuffixed artifacts are now the Jakarta ones: replace cibseven-engine-rest-core-jakarta with cibseven-engine-rest-core, cibseven-engine-rest-jakarta with cibseven-engine-rest, cibseven-engine-cdi-jakarta with cibseven-engine-cdi, cibseven-ejb-client-jakarta with cibseven-ejb-client and cibseven-spin-dataformat-xml-dom-jakarta with cibseven-spin-dataformat-xml-dom. Application servers with javax APIs (Tomcat 9, WildFly 26 and older, JBoss EAP 7) are no longer supported. ServletProcessApplication is now based on jakarta.servlet and deprecated in favor of JakartaServletProcessApplication. See Java EE variants removed.
  • Jakarta EE 11 and EL 6.0. All modules are built against Jakarta EE 11.0.0. cibseven-juel no longer contains its own copy of the EL API (org.cibseven.bpm.impl.juel.jakarta.el): custom EL classes such as an ELResolver, and process applications that override getElResolver(), getBeanElResolver() or initProcessApplicationElResolver(), must import jakarta.el and be recompiled. EL 6.0 removed ELResolver#getFeatureDescriptors, so custom resolvers that override or call it no longer compile; subclasses of the JUEL ExpressionFactoryImpl that override coerceToType must use <T> T coerceToType(Object, Class<T>). cibseven-engine-dmn brings jakarta.el-api 6.0.1 and the EL implementation Expressly 6.0.0; exclude Expressly from WAR and EAR files for Tomcat, WildFly and JBoss EAP, whose EL implementation applies. EL 4.0 is not supported; Jakarta EE 10 servers (e.g. Tomcat 10.1, JBoss EAP 8.1) remain compatible. Builds that import the Jakarta EE BOM next to CIB seven should use 11.0.0. See Jakarta EE 11, Jakarta Expression Language 6.0 and ELResolver#getFeatureDescriptors removed.
  • JAX-RS 4.0. The REST API (cibseven-engine-rest-core) and its wars are built against Jakarta RESTful Web Services 4.0. Custom JAX-RS resources, providers and REST extensions must run on JAX-RS 4.0, which dropped Link.JaxbLink / JaxbAdapter and @ManagedBean support. The REST API war of the Tomcat distribution ships RESTEasy 7.0.5.Final; RESTEasy 7 no longer has resteasy-netty4, so an embedded RESTEasy server needs resteasy-undertow or resteasy-jdk-http. See Jakarta RESTful Web Services 4.0.
  • Jackson 3 in the REST API. engine-rest uses Jackson 3 (tools.jackson); the JSON on the wire is unchanged. Jackson types in its public Java API are Jackson 3 types (tools.jackson.databind.ObjectMapper, ContextResolver<ObjectMapper> for REST extensions). JacksonConfigurator.configureObjectMapper(ObjectMapper) is replaced by configureObjectMapper(), which returns the configured JsonMapper. Applications that register com.fasterxml.jackson.jakarta.rs.json.JacksonJsonProvider must register CibsevenJacksonJsonProvider instead. See Jackson 3.
  • Jackson 3 in Spin and the external task client. cibseven-spin-dataformat-json-jackson, cibseven-spin-dataformat-all and cibseven-external-task-client use Jackson 3; stored JSON keeps the Jackson 2 format, and object variables written by 2.x are read as Jackson 2 read them (e.g. Map and Set properties with enum keys, classes with @JsonUnwrapped, and, with the Spring Boot starter, classes with a constructor without parameters next to one taking all properties). Data format configurators get an immutable Jackson 3 mapper (use rebuild()). Where Spin sees the annotations of variable classes (not in Run and the Tomcat distribution), the annotations of jackson-databind 2 (com.fasterxml.jackson.databind.annotation) are ignored, class ids on properties of type Object are no longer read without a PolymorphicTypeValidator, and @JsonInclude(content = NON_NULL) on a class drops null entries of its Map properties. Reading such a variable stores its new form, so back up the database before the update, and in a rolling update update all nodes before such variables are read. Applications that cannot move yet can use the deprecated cibseven-spin-dataformat-json-jackson2, cibseven-spin-dataformat-all-jackson2 and cibseven-external-task-client-jackson2 artifacts, which will be removed in 3.1.0; the two variants must not be on one classpath (the client fails with TASK/CLIENT-01035). Spin JSON needs json-path 3.0.0: applications using spring-boot-starter-parent must import the cibseven-bom before spring-boot-dependencies or set json-path.version, otherwise Spin fails with SPIN/JACKSON-JSON-01018.
  • No Jackson 2 in the Spring Boot starters, Run and the wars. cibseven-bpm-spring-boot-starter-rest and -webapp no longer bring Jackson 2. The core of CIB seven Run has no Jackson 2 unless the webclient or the AI Agent Connector is enabled, so process engine plugins and delegates in configuration/userlib/ that need Jackson 2 must bring it. The REST API war on WildFly excludes the server’s Jackson 2 modules. The Jackson modules of CIB seven on WildFly have the slot cibseven instead of their Jackson version; a process application whose jboss-deployment-structure.xml names the old slot does not deploy (WFLYSRV0179), see Jackson modules in jboss-deployment-structure.xml. The starter’s Jackson 2 configurators (CamundaJacksonFormatConfiguratorJSR310, …Jdk8, …ParameterNames) are only active with the -jackson2 Spin variant and are deprecated.
  • Spring Boot 4.1 and Spring Framework 7 only. Spring Boot 3 and Spring Framework 5 and 6 are no longer supported. The Spring Boot starters and CIB seven Run are built on Spring Boot 4.1; the former -4 artifacts (e.g. cibseven-bpm-spring-boot-starter-4, cibseven-bpm-run4) are Maven relocations to the unsuffixed ones and will be removed in a future release. cibseven-engine-spring is built on Spring Framework 7, cibseven-engine-spring-6 is removed and cibseven-engine-spring-7 relocates to cibseven-engine-spring. The webclient (cibseven-webclient-web) runs on Spring Boot 4 only; cibseven-webclient-web-spring-boot-4 is a relocation, and so is cibseven-webclient-web-ee-spring-boot-4 to cibseven-webclient-web-ee (EE exclusive). CIB seven 3.0 supports Spring Boot 4.1 with the Jackson 3 version it manages (3.1.7); Spring Boot 4.2 and Jackson 3.2 are not supported yet, since the REST API loses the resource type of filters with Jackson 3.2, and will follow with CIB seven 3.1. See Spring Boot Version Compatibility and Spring Boot 4 and Spring Framework 7 are required.
  • Quarkus 3.33. The Quarkus Extension is built on Quarkus 3.33.3 instead of 3.27; applications that use it must run on Quarkus 3.33.x. See Quarkus 3.33 extension update and Quarkus Version Compatibility
  • run4 becomes run. The Spring Boot 4 distribution of CIB seven Run is now the only one, named cibseven-bpm-run. The run4 Docker images are no longer built; use the run images.
  • Legacy Camunda web applications removed. Cockpit, Tasklist, Admin and Welcome (/camunda/app/…) are no longer shipped with the Tomcat and WildFly distributions, CIB seven Run, the Spring Boot starter-webapp and the BOM, and the cibseven-webapp-* wars are no longer published. Use the CIB seven webclient (/webapp). Plugins written for the legacy web applications no longer work. See Configuration Changes for the removed properties.
  • WildFly 28 distribution removed. The WildFly distribution is based on WildFly 42; the javax distributions for Tomcat 9 and WildFly 26 are removed as well.
  • JUnit 4 test support removed. ProcessEngineRule and DmnEngineRule are no longer JUnit 4 rules, and ProcessEngineTestCase no longer extends junit.framework.TestCase. The Spring Boot test starter no longer brings the JUnit Vintage engine, and JUnit 3-style test*() methods of ProcessEngineTestCase subclasses need @Test. Migrate process tests to JUnit 5, e.g. with ProcessEngineExtension from cibseven-bpm-junit5, see JUnit 4 and JUnit 3 test support removed.
  • GraalJS 25. The distributions update GraalJS from 21.3 to 25.0.1. Applications that embed the engine and bring GraalJS themselves declare org.graalvm.js:js with <type>pom</type>, and add com.ibm.icu:icu4j if their code or scripts use com.ibm.icu, which GraalJS no longer brings (the distributions keep icu4j 71.1). Manual Tomcat and WildFly installations replace the GraalJS jars and modules. A GraalJS context created with js.nashorn-compat needs js.ecmascript-version, otherwise its scripts are limited to ECMAScript 5. A script still stores an integer in the int range that comes from Java as a long as Integer, as in 2.2, but the result of arithmetic with it is now Double, so Java code that casts such a variable to Integer fails with a ClassCastException; the new process engine property javaScriptNumberNarrowing controls this. Incident messages of failed scripts no longer contain org.graalvm.polyglot.PolyglotException, so monitoring rules, alerts and tests that look for it need to be adapted. See Java 25 and GraalJS 25, Number types in JavaScript scripts and Script error messages.
  • MIME types of file variables. Variables.fileValue(File) detects the MIME type with Jakarta Activation 2.1 and Eclipse Angus. Manual Tomcat installations copy jakarta.activation-api and angus-activation to lib/; web applications that use the shared engine of Tomcat must not bundle them, otherwise every file gets application/octet-stream. Manual WildFly installations take the modules cibseven-commons-typed-values and cibseven-engine from the 3.0 distribution. See Jakarta Activation and MIME types of file variables.
  • New index on the historic job log. The update script creates ACT_IDX_HI_JOB_LOG_DEPLOYMENT on ACT_HI_JOB_LOG(DEPLOYMENT_ID_) and fails if an index of this name exists, on Oracle also if another index covers this column; drop such an index before the update. Building the index on a large job log takes time, and on PostgreSQL, Oracle and SQL Server it blocks writes to ACT_HI_JOB_LOG, and with them the job executor. See New database indexes.
  • The webclient tables are an optional schema component, off by default for embedded engines. The modeler, chat and notification tables are created with the engine schema only if the new process engine property webclientExtensionsEnabled is true (default false). It replaces modelerEnabled (default was true), which remains as a deprecated alias. The Tomcat, WildFly and Run distributions set it to true; an application that embeds the engine (e.g. with the Spring Boot starter) together with the webclient must set it. When the engine reports no webclient tables, the modeler, the chat, the notifications and the AI chat are switched off regardless of the webclient properties, and their endpoints answer 404; engines before 3.0 and a webclient whose tables have a DataSource of their own (cibsevenDataSource) behave as before, see Engine Switch. The SQL scripts for these tables ship separately as <db>_extensions_<version>.sql and <db>_extensions_2.2_to_3.0.sql, see Database Schema and Webclient database tables are now optional.
  • The chat, the notifications and the BPMN AI Agent need the engine’s webclient tables (EE exclusive). With an engine that reports no webclient tables (webclientExtensionsEnabled not set), these features stay off whatever the webclient properties say, and their endpoints answer 404. An installation that used the chat or the BPMN AI Agent with 2.2 and embeds the engine must enable webclientExtensionsEnabled.
  • Team chat transport (EE exclusive). The chat now uses long polling by default; set cibseven.webclient.modeler.chat.transport: websocket to keep the WebSocket transport of 2.2.
  • Restart and modification run custom listeners and input/output mappings by default (EE exclusive). “Skip custom listeners” and “Skip IO mappings” are no longer checked by default in restart and modification; check them when an operation must not run them.
  • Webclient configuration. The webclient no longer ships an application.yaml; its defaults are defined in code, and cibseven-webclient.yaml / cibseven-webclient.properties are read in every setup. The framework defaults of the standalone webclient (multipart sizes, spring.jpa.open-in-view, the Swagger UI path, …) apply only when the webclient runs on its own, and it no longer overrides the Spring Boot settings of a host application.
  • Webclient JSON. The webclient reads and writes JSON with Jackson 3 and its own mapper; it no longer defines an objectMapper bean, so an embedding application’s spring.jackson.* settings no longer affect it. JWT handling uses jjwt-gson instead of jjwt-jackson, and public types of cibseven-interfaces changed accordingly.
  • Modeler endpoints require the application ACCESS permission on modeler; authenticated users without it get 403. This also applies to the diagram history and the chat (REST and WebSocket) (EE exclusive). cibseven.webclient.modeler.authentication.enabled (cibsevenmodeler.authentication.enabled) is removed, the modeler and the chat always require authentication. See Authentication.
  • Process keys and form ids are unique per folder in the modeler instead of across all models; several folders may hold models with the same key, and deploying any of them adds a version to the same process definition. The webclient tables need the update script <db>_extensions_2.2_to_3.0.sql (Liquibase changeset 2.2-to-3.0-extensions), which replaces the unique keys with MOD_UK_DIAGRAMS_KEY_FOLDER and MOD_UK_FORMS_FORMID_FOLDER; without it, the webclient keeps working, but keys stay unique across all folders. See Folders.
  • External task retries with a retry time cycle. A camunda:failedJobRetryTimeCycle modeled on an asyncBefore / asyncAfter external task now also limits the external task itself: each fetch consumes one retry, independent of what a worker reports with handleFailure. See Retry Time Cycle
  • AI Agent Connector chat log stored in chunks. The chat log of an activity is written as one variable per model call, cibseven-connect-ai-agent_<activityId>~<eventSeq>, after the single cibseven-connect-ai-agent_<activityId> variable of earlier versions, which is still read. Custom readers of the chat log must read the chunks.
  • Delete deployments batch (since 2.2.5). A “Delete deployments” batch that stalled before the update does not resume; delete it and start it again, see Stalled “Delete deployments” batches.
  • Attachment permissions (since 2.2.5). Reading, creating, changing and deleting the attachments of tasks and process instances now requires a permission on the task or process instance, including the tenant check. Users who used attachments without such a permission now get an AuthorizationException (HTTP 403 over the REST API). Reading needs READ on the task or READ_TASK on the process definition, or READ on the process instance or READ_INSTANCE on the process definition; writing needs TASK_WORK or UPDATE on the task, or TASK_WORK or UPDATE_TASK on the process definition, or UPDATE on the process instance or UPDATE_INSTANCE on the process definition. Attachments of completed tasks and process instances are checked against the history permissions: READ_HISTORY on the process definition to read (or READ on the historic instance with enableHistoricInstancePermissions), and DELETE_HISTORY on the process definition or ALL on the historic instance to write. Attachments whose task or process instance no longer exists are available to administrators only. Setting the process engine property enforceAttachmentPermissions to false restores the previous behavior (not recommended). The checks only apply when authorization or the tenant check is enabled. See Attachment and Comment Permissions
  • Comment permissions (since 2.2.5). Creating and reading the comments of tasks and process instances, and reading task events, now requires a permission on the task or process instance, including the tenant check: READ on the task or READ_TASK on the process definition to read, TASK_WORK or UPDATE on the task or UPDATE_TASK on the process definition to add, and READ / UPDATE on the process instance or READ_INSTANCE / UPDATE_INSTANCE on the process definition for process instance comments. Comments of completed tasks and process instances follow the history permissions, so the former assignee of a completed task needs READ_HISTORY on the process definition, or READ on the historic task with enableHistoricInstancePermissions, to keep reading its comments. Creating a task comment over the REST API now answers HTTP 403 instead of 400 on a missing permission. Setting the process engine property enforceCommentPermissions to false restores the previous behavior (not recommended); updating and deleting comments stay checked either way. See Attachment and Comment Permissions
  • JUEL scripts with a customized expression manager (since 2.2.5). If the process engine uses a subclass of JuelExpressionManager, SpringExpressionManager or CdiExpressionManager, or a SpringExpressionManager with the property beans set, scripts with scriptFormat="juel" (in script tasks, listener scripts, conditions and input/output mappings) now resolve names, properties and methods through the expression manager’s resolver chain, like attribute expressions. In these cases only: the restrictions of the expression manager, including those on top-level names, now apply in JUEL scripts, and script expressions it rejects fail; names that only the script resolver factories provided (configuration beans, Spring beans, mocks, custom ResolverFactory implementations) are no longer available; context, and with it lang:import, is no longer available; a process variable takes precedence over a bean with the same name; unknown names fail with “Cannot resolve identifier”; and, as in attribute expressions, authenticatedUserId, externalTask, caseExecution, execution in task listener scripts, process application beans and CDI beans are now available. Test your JUEL scripts against your expression manager before the update. Overriding JuelExpressionManager#isAppliedToJuelScripts to return false keeps the previous behavior, and with it the security issue this change fixes. An expression manager that is not a JuelExpressionManager does not affect JUEL scripts, and the engine logs the warning ENGINE-21004. Engines with a stock expression manager, and script languages other than JUEL, are not affected; no configuration change is needed. See Custom Expression Managers
  • AI Agent Connector API key (since 2.2.5). The server’s key OPENAI_API_KEY is now sent only to the endpoint configured on the server: OPENAI_BASE_URL, or the OpenAI API if it is not set. A process that sets baseUrl to another provider and relied on the server’s key now calls that provider without a key; set OPENAI_BASE_URL on the server to that provider instead. See API key and endpoint
  • Swagger UI version setting (since 2.2.5). The Swagger UI uses swagger-ui 5.34.1, which springdoc only serves when springdoc.swagger-ui.version names it. The standalone webclient sets it from the shipped webjar, and the shipped default.yml / production.yml of CIB seven Run set it. If you run CIB seven Run with your own configuration file, or embed the webclient in your own Spring Boot application, set springdoc.swagger-ui.version: 5.34.1; otherwise the Swagger UI answers HTTP 404
  • Deny list for expressions and scripts active by default. Expressions and JUEL scripts are now checked against the deny list without any configuration; on 2.2.5 it was only active once deniedExpressionAccess was set. It applies to BPMN and CMMN expressions, JUEL scripts, DMN JUEL expressions and the legacy FEEL engine. Expressions and JUEL scripts that use reflection or Class objects (class, getClass), lang:import, the process engine configuration, java.lang.Runtime or java.lang.ProcessBuilder now fail. Start with expressionHardeningMode=report, which only logs the warning ENGINE-25010, and switch to enforce once the log is clean; a leading minus in deniedExpressionAccess allows a single default again (e.g. -lang:import), and expressionHardeningMode=off restores the previous behavior (not recommended). See Deny list for expressions and scripts
  • AI Agent Connector default model. An AI agent activity or agentic ad hoc sub process without a model now runs on gpt-6-luna instead of gpt-5.4-nano, which in an agentic ad hoc sub process started waiting tools twice and passed made-up arguments. Set CIBSEVEN_CONNECT_AI_AGENT_DEFAULT_MODEL (or the system property cibseven.connect.ai-agent.defaultModel) on the server to keep the previous model. See Recommended Models
  • SLF4J 2 (since 2.2.4). The engine manages slf4j-api 2.0.18 and logback 1.5.38. Applications that embed the engine with an SLF4J 1.x binding must switch to an SLF4J 2 provider, e.g. log4j-slf4j2-impl instead of log4j-slf4j-impl.
  • Task filter expression whitelist enabled by default (since 2.2.4). Task filter expressions outside the whitelist are rejected with HTTP 400, and a stored filter that uses one shows an error in the Tasklist.
  • First-admin setup only on an unconfigured engine (since 2.2.4). The initial setup is offered only while the identity service is writable, holds no users, groups or authorizations, and no administrators are configured besides camunda-admin. An installation without an administrator must configure one via admin-user or adminUsers.
  • AI Agent Connector memoryId scoped to one process instance (since 2.2.4). A memoryId no longer continues a conversation in another process instance and may be at most 222 characters long, see chat memory.
  • Prometheus metrics in the Docker images (since 2.2.2). The OpenTelemetry Java agent 2.28.1 exports the CPU utilization metrics as os_cpu_recent_utilization and os_system_cpu_utilization, without the _ratio suffix; update dashboards and alerts that use the old names. The images set OTEL_EXPORTER_PROMETHEUS_HOST=0.0.0.0 (see Configuration Changes).

Configuration Changes

  • webclientExtensionsEnabled: new process engine property (default false) that decides whether the engine creates, drops and checks the webclient tables (modeler, chat, notifications). It is set to true in the Tomcat (bpm-platform.xml), WildFly (standalone.xml) and Run (default.yml, production.yml) distributions. modelerEnabled is deprecated and sets the same switch. The Docker images accept WEBCLIENT_EXTENSIONS_ENABLED=false to leave the tables out.
  • externalTaskFailedJobRetryTimeCycle: new process engine property (e.g. R5/PT25S), the engine-wide retry cycle for external tasks without a cycle of their own.
  • javaScriptNumberNarrowing: new process engine property (default long): a JavaScript script returns an integer in the int range that comes from Java as a long to Java as Integer, as in 2.2; none gives the GraalJS 25 types Long and Double. It applies only with configureScriptEngineHostAccess; if the process engine cannot apply it, every JavaScript script fails with ENGINE-21006. See Number types in JavaScript scripts.
  • CIB seven Run --ai and MCP_ENABLED: the libraries of the AI Agent Connector, agentic ad hoc sub processes and the REST API MCP plugin in configuration/userlib-ai/ are on by default and off with --production unless --ai is given. The environment variables AI_AGENT_ENABLED and the new MCP_ENABLED override this: if either is set, the libraries are on when at least one of them is true. The MCP server (/mcp) itself runs only with MCP_ENABLED=true (spring.ai.mcp.server.enabled and cibseven.mcp.restapi-mcp in default.yml and production.yml), also when the AI agent is on. The run Docker image passes MCP_ENABLED through (unset by default). See AI Agent connector and REST API MCP
  • CIB seven Run actuator: Run ships Spring Boot Actuator with health and info exposed read-only, configured with the Spring Boot 4 property names (management.endpoints.access.default, management.endpoint.{health,info}.access).
  • Spring Boot starter: camunda.bpm.webapp keeps only enabled, application-path, webjar-classpath and index-redirect-enabled; the properties of the legacy web applications (csrf, session-cookie, header-security, auth, security-config-file) and camunda.bpm.webapp.installed are removed. cibseven.webclient.cockpit.url is removed from Run.
  • Webclient frontend plugins: cibseven.webclient.plugins.enabled (default false) and cibseven.webclient.plugins.disabled (plugin ids to skip), see Frontend Plugins.
  • Deep links: new deepLinks section in config.json and Helm value ui.deepLinks, see Deep Links.
  • SSO logout: new cibseven.webclient.sso.endpoints.revocation (token revocation on logout) and cibseven.webclient.sso.endpoints.endSession (OIDC RP-initiated logout; register <app url>/ as post-logout redirect URI at the identity provider).
  • Webclient persistence: new cibseven.webclient.persistence.properties.* for Hibernate settings of the webclient’s own persistence unit (e.g. hibernate.default_schema); spring.jpa.hibernate.* of the application no longer applies to it. See cibseven.webclient.persistence.properties and Database.
  • Default start form (since 2.2.2): cibseven.webclient.startProcess.defaultFormEnabled (default false) shows a default start form with a business key and process variables for process definitions without a start form of their own; with false, such a process starts at once.
  • Removed webclient properties: cibseven.webclient.custom.spring.jackson.serialization.write-dates-as-timestamps (ignored with a warning; dates are always ISO-8601, see Patch Level Update), cibseven.webclient.deprecated.authorization.enabled (permissions are checked by the engine only), cibseven.webclient.modeler.authentication.enabled, and cibseven.webclient.fetchInstances and cibseven.webclient.fetchIncidents (they had no effect).
  • History level fallback: cibseven.webclient.historyLevel falls back to audit (the engine default) instead of full; it is used only when the engine does not report its history level.
  • Permission keys: suspendProcessInstance is removed from config.json, the built-in defaults and the Helm values; displayTasks, deleteProcessInstance and deleteHistoricProcessInstance were removed (since 2.2.4). Configurations that still contain them are not affected.
  • Authorization resource types: in config.json / Helm admin.resourcesTypes, system now offers READ, SET and DELETE; optimize, operationLogCategory and report were removed; admin.types ids are numeric.
  • Helm: the config.json ConfigMap is now mounted where the webclient reads it, so overrides take effect.
  • Chat transport (EE exclusive): new cibseven.webclient.modeler.chat.transport with longpolling (default) or websocket; with long polling, presence is kept in the database. See Enable / Disable.
  • Snapshot retention renamed (EE exclusive): cibsevenmodeler.deleteProcesses.versionLimit → cibseven.webclient.modeler.history.versionLimit and cibsevenmodeler.deleteProcesses.cron → cibseven.webclient.modeler.history.cron; they apply to forms too. The old names are still read with a warning. cibseven.webclient.modeler.history.maxResults (default 30), which limits the snapshots listed, replaces cibseven.modeler.historicMaxResults; the old name is no longer read. See Modeler configuration.
  • Notifications (EE exclusive): new cibseven.webclient.notifications.enabled (default false) and config.json notifications.system.interval (default 120000 ms), also as Helm values. See Notifications.
  • Enterprise defaults (EE exclusive): the enterprise webclient’s defaults (SevenProviderEE, page title, BPMN AI Agent model catalog) apply with the lowest precedence; a configured community provider class (SevenProvider, SevenDirectProvider) is replaced by its enterprise counterpart with a warning instead of failing the start.
  • BPMN AI Agent (EE exclusive): new limit cibseven.webclient.modeler.ai.limits.currentFormSchemaMaxChars (default 200000) for the form schema sent per request; per-model vision flag (cibseven.webclient.agent.models[].vision, default true) (since 2.2.2).
  • Envers (EE exclusive): spring.jpa.properties.hibernate.integration.envers.enabled is no longer needed; the modeler writes its snapshots itself.
  • License chunks (EE exclusive): cibseven.webclient.license.chunk.trustServerAuthentication leaves the authentication of licensed frontend chunks to the server (since 2.2.3).
  • enableFilterExpressionWhitelist default changed from false to true (since 2.2.4); use allowedFilterExpressions to allow additional expressions.
  • AI Agent Connector chat memory (since 2.2.4): cibseven.connect.ai-agent.chatMemoryVariable.enabled (default true) and cibseven.connect.ai-agent.chatMemoryMaxPayloadBytes (default 1 MiB).
  • OTEL_EXPORTER_PROMETHEUS_HOST (since 2.2.4 hotfix): the Docker images set it to 0.0.0.0, so the Prometheus exporter can be scraped from outside the container when it is enabled. Restrict access to port 9464, or set it to localhost.
  • New process engine property enforceAttachmentPermissions (default true): permission and tenant checks for attachments, see Breaking Changes. In CIB seven Run / Spring Boot, set process engine properties via camunda.bpm.generic-properties.properties.<name> (since 2.2.5)
  • New process engine property enforceCommentPermissions (default true): permission and tenant checks for comments, see Breaking Changes (since 2.2.5)
  • New process engine property deniedExpressionAccess (default: not set, only the built-in entries apply): comma-separated entries added to the deny list for JUEL expressions and scripts, which is active by default since 3.0.0, see Security Hardening (since 2.2.5)
  • New process engine property executionAllowList (default: empty, no check): a comma-separated allow list of task types and script languages, see Security Hardening (since 2.2.5)
  • New process engine property expressionHardeningMode (off, report or enforce, default enforce): what happens on a violation of the deny list or, once it is set, of executionAllowList, see Hardening Mode (since 2.2.5)
  • New connector setting cibseven.connect.allowed-endpoints (system property) / CIBSEVEN_CONNECT_ALLOWED_ENDPOINTS (environment variable), and per connector cibseven.connect.<connectorId>.allowed-endpoints / CIBSEVEN_CONNECT_<CONNECTOR_ID>_ALLOWED_ENDPOINTS (default: not set, no restriction), see Security Hardening (since 2.2.5)
  • The shipped configuration of CIB seven Run sets springdoc.swagger-ui.version: 5.34.1, and the standalone webclient sets it from the shipped webjar, see Breaking Changes (since 2.2.5)
  • AI Agent Connector default model: gpt-6-luna instead of gpt-5.4-nano for activities without a model; CIBSEVEN_CONNECT_AI_AGENT_DEFAULT_MODEL / cibseven.connect.ai-agent.defaultModel sets another one, see Breaking Changes
  • H2 lock timeout: the process engine now acquires its exclusive locks, e.g. the deployment lock, on H2 2.x too, and the H2 JDBC URLs of the distributions set ;LOCK_TIMEOUT=10000 (H2 default: 2 seconds). Add it to your own H2 JDBC URL, otherwise a long deployment or cascading deletion can make a concurrent one fail with an H2 lock timeout. See Deployments in a Clustered Scenario
  • Webclient connection pool: cibseven.webclient.rest.maxConnPerRoute defaults to 100 instead of 20, and maxConnTotal (2 × maxConnPerRoute) to 200 instead of 40, since the webclient’s GET requests to the engine REST API now use this pool too; also in the Helm values. Up to 2.2, each GET request opened a connection of its own, without a limit and without a read timeout. Now a request waits up to connectionRequestTimeout (180 s) for a free connection and then fails, and socketTimeout (3600 s) also limits GET requests. Raising the pool is only needed for more than 100 parallel requests per engine, see Core Configuration

New Features

Ad Hoc Sub Process

  • The BPMN adHocSubProcess element is supported in the model API (AdHocSubProcess, fluent builder), the engine and the REST API. Entering the scope starts nothing; activities without an incoming sequence flow can be started by a client, and the scope completes by its completionCondition or when nothing is active any more
  • RuntimeService#activateAdHocSubProcessActivities(...), createAdHocSubProcessActivation(executionId) and completeAdHocSubProcess(...), and the REST endpoints POST /execution/{id}/ad-hoc-activities/activate and POST /execution/{id}/ad-hoc-activities/complete; they require UPDATE on the process instance or UPDATE_INSTANCE on the process definition
  • Deployments are refused for an ad hoc sub process without activities, with start or end events, with ordering="Sequential" or triggeredByEvent="true"

Agentic Ad Hoc Sub Process (beta)

  • An ad hoc sub process that carries the AI Agent Connector is driven by a model: each turn asks the model which activities to start as tools, feeds their results back, and ends the sub process when the model is done; turn and call limits end it with a BPMN error
  • The agent is told how each tool ended (completed, waiting, interrupted by a boundary event, cancelled) and sees the declared process variables on every model call
  • New element template cibseven-ai-agent-adhoc.json; enabled together with the AI Agent Connector
  • Beta: works for limited use cases and is under active development.

AI Agent Connector

  • New inputs contextVariables and optionalContextVariables: the named process variables are sent to the model after the system prompt; a missing required variable fails the activity before the model is called
  • New input documents: file or bytes variables (PDF, PNG/JPEG/GIF/WebP images, text, JSON, XML, YAML) are sent to the model, up to 5 MiB per document and 10 documents in total
  • The audit trail records which variables and documents were sent (name, type, size, SHA-256), never their values
  • The conversation is written once per step and the chat log once per model call, which reduces history rows at history level full
  • The bundled element templates and the Javadoc no longer suggest passing an API key in a process variable or a credential in the BPMN XML; they point to the server’s OPENAI_API_KEY and say where a token in a header field is stored (since 2.2.5)
  • The default model is gpt-6-luna instead of gpt-5.4-nano, set on the server with CIBSEVEN_CONNECT_AI_AGENT_DEFAULT_MODEL; both element templates show it as the placeholder of the empty Model field, and the agentic ad hoc template recommends a model built for tool calling
  • The chat memory is stored as a process variable per process instance, survives restarts and is shared between replicas (since 2.2.4)

REST API MCP Plugin in CIB seven Run

  • CIB seven Run ships the REST API MCP Plugin (cibseven-mcp-restapi) in configuration/userlib-ai/; it is off by default and switched on with MCP_ENABLED=true, in production.yml as well; see AI Agent connector and REST API MCP
  • The MCP tools are built from the openapi.json of the REST API of this version, shipped with Run, so the tools match the engine and the startup needs no internet access

External Tasks

  • camunda:failedJobRetryTimeCycle applies to external tasks: each fetch consumes one attempt, the cycle’s interval delays the next one, and a failedExternalTask incident is raised when the last attempt is fetched, so a worker that dies without handleFailure no longer fetches a task forever, see Retry Time Cycle
  • At history level full, every fetch writes a fetched entry to the historic external task log (worker id, topic, priority, remaining retries); query it with HistoricExternalTaskLogQuery#fetchedLog() or GET /history/external-task-log?fetchedLog=true. The entry is written in the same transaction as the lock of the task: if it cannot be written, the fetch fails and the worker gets no tasks, and a custom history event handler sees the event before the commit, see History of Fetches

Authorization

  • New endpoint GET /authorization/self returns the authorizations that apply to the current user. The webclient uses it to decide which UI elements to show, so ordinary users no longer need a global READ authorization, see Authorizations and access to UI features
  • The Report and Dashboard authorization resources are deprecated; nothing in CIB seven checks them any more

Security Hardening

The allow list for task types and script languages and the endpoint allow list are off by default, so an engine behaves as before until an administrator sets them. The deny list for expressions and scripts is active by default since 3.0.0, see Breaking Changes; on 2.2.5 it was only active once deniedExpressionAccess was set. (since 2.2.5)

  • Deny list for expressions and scripts: deniedExpressionAccess names what JUEL expressions and scripts must not access: a property or method name (getClass), a type (java.lang.Runtime), an EL function (lang:import) or a member of a type (com.example.Admin#delete). It applies to BPMN and CMMN expressions, JUEL scripts, DMN JUEL expressions and the legacy FEEL engine, not to other script languages. The list is active by default with the defaults class, getClass, java.lang.Class, java.lang.ClassLoader, java.lang.reflect.AccessibleObject, java.lang.invoke.MethodHandle, java.lang.invoke.MethodHandles, lang:import, org.cibseven.bpm.engine.impl.cfg.ProcessEngineConfigurationImpl, java.lang.Runtime and java.lang.ProcessBuilder; a leading minus removes a default (e.g. -lang:import). A newly denied EL function can stop deployed process definitions from loading, so run with expressionHardeningMode=report first, which only logs violations (since 2.2.5)
  • Allow list for task types and script languages: once executionAllowList has entries, process definitions can only use the listed built-in task types (shell, mail, external) and script languages, checked at deployment and at execution. For example, external, mail, juel, groovy, javascript, feel allows mail tasks and denies shell tasks (since 2.2.5)
  • Endpoint allow list for connectors: cibseven.connect.allowed-endpoints restricts the endpoints the HTTP and SOAP connectors (including redirects) and the AI Agent Connector (model endpoint, MCP servers, PostgreSQL and embedding endpoints) may contact, so that targets taken from process variables cannot send requests and credentials elsewhere. Entries have the form scheme://[*.]host[:port], separated by commas. A connector’s own setting (cibseven.connect.<connectorId>.allowed-endpoints, e.g. http-connector, soap-http-connector, cibseven-ai-agent) replaces the global one, and * exempts it (since 2.2.5)

REST API

  • GET /configuration also returns historyTimeToLive and enforceHistoryTimeToLive

Java 25

  • CIB seven runs on Java 25 in addition to Java 17 and 21; the Docker images are also built for Java 25 with a java25- tag prefix (e.g. cibseven/cibseven:java25-tomcat-latest), while Java 21 stays the default
  • GraalJS 25.0.1: with enableScriptEngineNashornCompatibility, scripts use ECMAScript 2022, so built-in objects such as Map, Set, Symbol and Promise are defined

Frontend Plugins

  • The webclient can be extended with frontend plugins: a plugin jar contributes tabs to process and decision definitions and instances, works on the DMN viewer, adds a banner below the header or an Admin entry
  • Plugins are disabled by default and can be switched off one by one
  • Administrators can configure deep links from process definitions, process instances, decision definitions and decision instances to external applications, shown as a tab or a button, without custom frontend code
  • New header navigation with grouped hover menus, a mobile menu, start tiles and hub pages; the header shows the theme logo with the product name
  • An unknown address, e.g. an outdated bookmark, opens the start page with a “page not found” message instead of a blank page
  • The text beside the logo is the translation key navigation.logoText; an empty value shows the logo alone

Process Definitions and Deployments

  • Compact version cards in the version sidebar of the process definition view, with expandable details that load the version’s data when they open
  • “Open in Modeler” for the diagram of a process definition and for BPMN and DMN resources of a deployment
  • Form-js and HTML form resources of a deployment can be previewed in the deployment view
  • The process definition diagram shows tokens waiting in asynchronous jobs and their incidents
  • The “unfinished instances” filter of the process definition view is kept across reloads
  • Processes without a configured start form can get a default start form with a business key and process variables; it is off by default and switched on with cibseven.webclient.startProcess.defaultFormEnabled (since 2.2.2)
  • The BPMN viewer’s pan and zoom position is kept across the process definition and process instance views (since 2.2.2)
  • The DMN viewport, panel size and sidebar state are kept across views (since 2.2.3)
  • The process instance filter in the BPMN viewer also applies to the historic activity statistics (since 2.2.1)

History Time To Live

  • Editing the history time to live of process and decision definitions offers “Unlimited”, “0 days”, the engine default and a custom value, shows the engine’s default and whether it enforces a time to live, and disables “Unlimited” when it does

Tasklist

  • Task cards and the opened task show the assignee’s name instead of the user id
  • Consistent headers on mobile devices in the task view, task list, filters and sidebar
  • The task list, filter panel and task header are optimized for mobile devices (since 2.2.4)

Variables

  • Each variable in the Variables tab offers Edit or a read-only View, and Bytes variables can be downloaded and uploaded as files (since 2.2.4)

Single Sign-On

  • On logout the webclient revokes the OAuth2 tokens and ends the session at the identity provider (OIDC RP-initiated logout), if the new endpoints are configured
  • OAuth2 authentication with assertion (JWT client authentication) (since 2.2.1)

LDAP

  • Configurable cache for LDAP authentication (since 2.2.1)
  • Configurable user objectClass, targeted lookup at login instead of a directory search, and no failure without a display name attribute (since 2.2.1)

Connectors in CIB seven Run

  • The http-client and soap-http-client connectors and their element templates ship with CIB seven Run in configuration/userlib/ (since 2.2.1)

Modeler Enhancements

  • Diagrams and forms are organized in folders: browse with a breadcrumb, create, rename, move and delete folders, and copy or move models into another folder; folders at the top level are projects, and an update puts all existing models into a folder named General
  • Every user gets a folder of their own on the first visit, and a star sets the folder the modeler opens by default
  • Process keys and form ids are unique per folder; a copy into another folder keeps its key, the deploy dialog warns when another model uses the same key, and a form referenced by a BPMN diagram is taken from the same folder first
  • New and imported models are stored in the open folder; folders and models are listed in a table with a search across all folders and a type filter
  • Models open read-only when the user may only view them, and the start page offers only the actions the user may perform
  • Search button next to the canvas controls of the BPMN and DMN editors
  • Tabs in the overflow menu can be closed there
  • Expanding a sub-process moves the neighboring elements aside instead of covering them
  • BPMN validation is aligned with Camunda 7.24: valid ad hoc sub processes no longer show errors, label-required, fake-join and no-inclusive-gateway are no longer reported, and no-implicit-end and no-gateway-join-fork are warnings
  • Element templates without a group are listed under Not categorized
  • Refreshed design of the toolbar, canvas buttons, tabs, console panel and dialogs
  • Multi-file import and deployment, drag and drop, deploying a process together with its forms, and download from the start page (since 2.2.1)
  • Plugin and chat extension points, grouped element-template scopes, collapsible side panel, close-all tabs, “Skip creation dialog” preference, and toast notifications with a redirect after starting a process (since 2.2.1)
  • Dedicated Create BPMN, Create DMN and Create Form actions on the start page (since 2.2.2)
  • New modeler endpoints GET services/v1/modeler/process/key-in-use, GET services/v1/modeler/form/key-in-use and GET services/v1/modeler/form/find-all-by-formid; find-by-key, find-by-formid and the reduced deploy take an optional folderId, see the modeler REST API
  • The full list of changes is in the release notes of cibseven-modeler 1.3.0

Notifications (EE exclusive)

  • Administrators publish notifications as a banner below the header of every page: with a severity (Information, Warning, Critical), an optional “More information” link and a validity period, for all users or members of selected groups
  • Users can dismiss a notification; the banner updates without a reload, and screen readers announce new notifications
  • Managed under Admin → Notifications, with the permissions READ, SET and DELETE on the System resource; off by default

Modeler EE Features (EE exclusive)

  • Project members: a project can be open or restricted to members, each with the role Project Admin, Editor or Viewer; Viewers open models read-only. See Project Members
  • The BPMN AI Agent is available only to Editors and Project Admins of a restricted project, and the team chat of a model only to members of its project
  • Form snapshots: every form save records a snapshot; earlier states can be browsed, restored and compared structurally. See Snapshots & Comparison
  • Autosave: opt-in autosave, switched on in the menu of the save button, with a “saved at” indicator. See Autosave
  • Element template management: add, edit and delete element templates in the modeler, in a table or a categorized view, with a form-based editor. See Template Management
  • Chat transport: long polling (default) works in multi-pod deployments without sticky sessions; WebSocket remains available
  • Updated Modeler EE user interface, and diagram diff failures are reported (since 2.2.1)

Form AI Agent (EE exclusive, beta)

  • New AI panel in the form editor: describe a form, or attach a screenshot, and review and apply the proposed schema. See Form AI Agent
  • Beta: works for limited use cases and is under active development.

BPMN AI Agent (EE exclusive, beta)

  • The BPMN AI Agent generates and previews embedded forms and Camunda Forms, and edits diagrams with an atomic patchXml tool (since 2.2.1)
  • A per-model vision flag lets a text-only model skip image and PDF attachments instead of the request being rejected (since 2.2.2)
  • Beta: works for limited use cases and is under active development.

Authorizations (EE exclusive)

  • The profile page of a user or group has an Authorizations tab that lists the authorizations assigned to it, optionally including those for all users (*); it is also reachable from the account menu

Process Definitions (EE exclusive)

  • A Migrate button on each process definition version card opens the migration for that version
  • The heatmap on/off choice is remembered

Agent Chat and External Tasks Log (EE exclusive)

  • The Agent Chat tab shows an activity’s chat log stored in chunks as one conversation; logs written before 3.0 are shown as before
  • The External Tasks Log shows the new “fetched” state

Batch Operations (EE exclusive)

  • New “Delete Deployments” batch operation with a deployment search and the cascade, skipCustomListeners and skipIoMappings options (since 2.2.2)
  • Batch operations the user has no permission for are hidden; they no longer require UPDATE, and “delete deployments” and “correlate message” are checked against CREATE_BATCH_DELETE_DEPLOYMENTS and CREATE_BATCH_CORRELATE_MESSAGE (since 2.2.4)
  • Comma-separated process instance ids in the “Id in” filter (since 2.2.1)

Process Instance Search and Modification (EE exclusive)

  • The dashboard and process definition views open the runtime or history process instance search according to the history level and the selection (since 2.2.3)
  • The process instances table offers stop and delete history according to the user’s permissions, also for internally terminated instances (since 2.2.4)
  • When modifying several instances, the instance search is preset to the instances at the activity being cancelled (since 2.2.4)
  • Bytes variables can be downloaded from the variable log (since 2.2.4)

Docker

  • WEBCLIENT_EXTENSIONS_ENABLED environment variable to override webclientExtensionsEnabled of the distribution in the Tomcat, WildFly and Run images
  • MCP_ENABLED environment variable for the run image to switch on the REST API MCP plugin

User Experience Improvements

Authorizations

  • Resource types in the Authorizations navigation are grouped, each resource type and application permission has a description, and the permission dropdown groups the permissions
  • The deprecated Optimize, Report, Dashboard and Operation Log Category resource types are no longer offered, and the System resource offers READ, SET and DELETE
  • An ALLOW for every user (*) is stored as a GLOBAL authorization, and a second GLOBAL authorization for the same resource is reported as a conflict
  • Batch authorizations offer CREATE_BATCH_DELETE_DEPLOYMENTS and CREATE_BATCH_CORRELATE_MESSAGE (since 2.2.4)
  • The Suspend and Activate buttons of the process instances list follow the engine’s permission checks, including grants on a single instance
  • The task assignment actions are shown only to users who may assign the task (since 2.2.4)
  • The “change password” menu item is shown only to users who may use it, and a warning is shown on the Authorizations page when authorization is disabled (since 2.2.2)

Users and Groups

  • Each tab of the account, user and group pages has its own URL; old links are redirected
  • A password refused by the password policy shows the policy’s message

Process Instances

  • With history level none: instance details, badges, the activity filter, called process instances and an incidents icon in the state column are shown (since 2.2.2, 2.2.3)
  • The BPMN viewer searches only unfinished process instances by default (since 2.2.2)

Execution Metrics

  • Copy button for each annual statistics item and a total for the last 12 months in Process Engine Metrics (since 2.2.3)
  • Monthly chart interaction, statistics per groupBy, and locale-aware number formatting (since 2.2.2)

Deployments

  • Deployment queries support all query parameters (name, source, tenant, deployment time) (since 2.2.2)

Process Instance Search (EE exclusive)

  • With history level none, the history search shows a warning, and the runtime search shows only the columns it can fill
  • Switching between runtime and history search keeps the last criteria of each mode
  • The search box’s focus ring surrounds the whole bar, and its suggestion menus can be used with the keyboard
  • Suspend and Activate are shown only to users who may suspend the instance

Cleanup (EE exclusive)

  • The tabs of Cleanup and its menu entry are shown only to users who may read the reports
  • The history time to live dialog is the one of the process definition view and can also set the default time to live; an unset time to live is shown as ∞

License (EE exclusive)

  • Saving a license key that the engine did not store now says why (no or different JWT secret, missing SET permission on System) instead of reporting success; the engine answers HTTP 503 with the cause
  • The license key can be edited by users with SET on the System resource; License Key is listed below Execution Metrics in the Admin menu

Enterprise Endpoints (EE exclusive)

  • The enterprise endpoints (batch operations, cleanup, migration, modification, reports, metrics, logs, process instance search) no longer run their own permission pre-checks, so users with fine-grained grants are no longer refused by the webclient

Migration (EE exclusive)

  • Link icons, tooltips and a responsive layout in the migration confirmation view (since 2.2.1)

Decisions

  • The decision instance view highlights the rows of the rules that fired

Accessibility

  • Search fields draw the focus ring around the whole field, all list searches use one search component, and table action buttons keep their keyboard focus outline
  • Task filters are rendered as real links in a list with aria-current, the task count is no longer announced every minute, and the task list header buttons are no longer nested
  • Form fields built with b-form-group have an accessible name again
  • Sortable table headers announce a valid aria-sort value
  • Badges are no longer announced on every change, and the decorative icon of the error dialog is hidden from screen readers
  • Keyboard focus on light buttons is shown as an outline
  • Copy buttons work reliably with the keyboard and confirm the copy to screen readers
  • Filter and date buttons of task cards are named for screen readers
  • Image icons stay visible in Windows High Contrast mode
  • In the Tasklist, Alt+3 moves the focus to the selected task again
  • Accessible labels on admin, process, task filter, tenant, deployment and settings controls (since 2.2.2); accessible labels and live region announcements in the Modeler (since 2.2.1)

Bug Fixes

Security

  • Task names, process names and error messages are now rendered as text in the task list navigation, the process lists, the start process dialog and error dialogs, closing a stored cross-site scripting (XSS) issue. Typing ( into the task or process search no longer causes an error (since 2.2.5)

  • Attachments of tasks and process instances could be read, downloaded, changed and deleted by any authenticated user who knew their id, since the engine did not check any permission; comments could be read and added the same way. Both are now checked, see Breaking Changes (fixes CVE-2026-109431) (since 2.2.5)

  • JUEL scripts (scriptFormat="juel") ignored the restrictions of a customized expression manager that applied to attribute expressions, so a restricted call such as reflection could still run in a script task. They now resolve through the expression manager, see Breaking Changes (since 2.2.5)

  • The Java External Task Client resolved external entities when it deserialized application/xml object variables, so a crafted variable could make a worker read local files and send requests to other hosts. External entities and DOCTYPE declarations are now rejected, also with a DocumentBuilderFactory supplied by the application (fixes CVE-2026-77224) (since 2.2.5)

  • The Docker images now ship a Java runtime with the fix for CVE-2026-114938 (“Java4Shell”). The ZIP distributions and the Spring Boot starter run on your own JDK: update it to 17.0.21.1, 21.0.13.1 or 25.0.5.1 or later, or start the JVM with -XX:-UseBASE64Intrinsics until you can (since 2.2.5)

  • The webclient connected to any host named in the X-Process-Engine request header, also before login, and echoed the URL and connection error in the response. It now accepts only engine ids whose engine REST server is configured, as cibseven.webclient.engineRest.url / path or as an entry of cibseven.webclient.engineRest.additionalEngineRest, and rejects requests for any other server with “The requested process engine is not configured”; connection errors are answered with “The process engine could not be reached” without details. The webclient UI, embedded forms and the SSO login take the engine id from the configured servers, so they work as before (since 2.2.5)

  • The webclient’s services/v1/system/pool-status endpoint answered without authentication; it now requires a login (since 2.2.5)

  • The AI Agent Connector sent the server’s OPENAI_API_KEY to any base URL a process supplied, for example in a process variable. The key is now sent only to the endpoint configured on the server, and the connector logs a warning for other endpoints (since 2.2.5)

  • Process descriptions and warnings are rendered as text in the start process list and the warning box, closing a stored cross-site scripting (XSS) issue (since 2.2.4)

  • The Swagger UI bundled DOMPurify 3.4.13, which is affected by GHSA-cg2g-xh64-v4q7 and GHSA-mrv2-3pqr-j5jr; it now bundles DOMPurify 3.4.17 (since 2.2.5)

  • The FEEL engine of the DMN engine called external Java functions, which the DMN engine disables, when a function definition was passed as an argument, e.g. to sort(); feel-engine 1.19.6 rejects such definitions (fixes GHSA-vx3p-v6cf-vfjw)

  • The webclient no longer logs the authentication response, including the token, to the browser console (since 2.2.4)

  • Task filter JUEL expressions can be restricted to a whitelist (since 2.2.2), which is enabled by default and also accepts the expressions suggested by the Tasklist filter dialog (since 2.2.4) (fixes Camunda Security Notice 157)

  • The first-run setup could create an administrator without login on an engine that was already administered; it is now offered only on an unconfigured engine (since 2.2.4) (fixes CVE-2026-77226, Camunda Security Notice 171)

  • The AI Agent Connector chat memory could be read from another process instance by reusing its memoryId (since 2.2.4)

  • Fixed a user query by id ignoring further criteria and the READ permission check (since 2.2.3)

  • Modeler: the edit lock is checked against its owner, /session/check no longer leaks the session id, and diagram XML parsing is hardened against XXE (since 2.2.1)

  • SSO: JWKS keys are matched by kid, x5t or x5t#S256, so tokens that identify their key by thumbprint are accepted

  • The team chat now passes every message through the server and checks every subscription and request against the project of the model, so users can no longer read or post in chats they may not access; chat messages are limited to 10,000 characters (EE exclusive)

Enterprise Features (EE exclusive)

  • Fixed “Unlimited” history time to live in Cleanup being saved as 0, so the history was removed by the next cleanup run, while the table showed ∞
  • Fixed “Delete all versions” of a process definition deleting only the newest version with the Direct Provider while reporting success
  • Fixed the Cleanup process instance report ignoring or failing on a process definition key filter, the Cleanup reports showing no result count, and the process instance duration report ignoring its process definition and period filters, with the Direct Provider
  • Fixed the license key not being stored in or read from an additional engine with its own jwtSecret
  • Fixed a criterion added while the process instance search or the batch operations list was loading being ignored
  • Fixed variable criteria with a quoted value in the process instance search: with =, !=, >, >=, < or <=, a quoted value such as "0100" is now sent as a string without the quotes, so it finds the variable; before, the quotes were sent along and nothing matched. Unquoted values are unchanged (since 2.2.5)
  • In the process instance search and in batch operations, a like value is now always sent as a string and wrapped in % unless it already starts or ends with %, so like 100 finds the String variables 100, 0100 and 1005. Switching a criterion from like to another operator removes the surrounding %. Saved searches, last-used criteria and URLs with like 100 therefore now also find 0100 and 1005. The engine compares like only for String variables, so an Integer variable 100 is found with = 100, not with like (since 2.2.5)
  • Fixed “Start after” being offered in process modification for activities with several or no outgoing flows, and cancelling a sub-process presetting a query that matched no instances
  • Fixed the migration wizard’s query mode migrating instances that did not match the filter (since 2.2.4)
  • Fixed “With incidents” in the history search matching resolved incidents, and incidents not loading with the Direct Provider (since 2.2.4)
  • Fixed “License Required” with a valid license when the authentication token is not in browser storage, and the service worker not claiming a reloaded page (since 2.2.3)
  • Fixed migration event triggers for receive tasks, timers and gateways (since 2.2.3)
  • Fixed the chat WebSocket endpoint under a path prefix (since 2.2.2) and in CIB seven Run (since 2.2.3)
  • Fixed ModelerViewEE loading element templates from the wrong path, the “correlate message” batch matching finished instances, and the variable filter “like” with non-string values (since 2.2.2)
  • Fixed the DMN viewer sidebar padding and Cleanup table cell padding (since 2.2.3)
  • Fixed edit locks not being released reliably, Modeler EE in Firefox, BPMN AI Agent chat history and session handling, and batch operation due dates (since 2.2.1)

Engine

  • Fixed jobs of the Quarkus Extension running without the Quarkus context class loader: a CDI bean with @ConfigProperty created while a job ran failed with SRCFG00015: No configuration is available for this class loader, and the job ended in an incident
  • Fixed cron timer cycles such as 0 0/15 * * * ? firing in an endless loop when clocks go back at the end of daylight saving time (since 2.2.5)
  • Fixed a backward-compatibility regression in the legacy Quartz cron syntax support (out-of-range steps, whitespace, day and month names in steps) (since 2.2.5)
  • Fixed the “Delete deployments” batch stalling with a deployment-aware job executor, the default of Tomcat and WildFly, after its first deployment or right away for deployments not registered on any node; its jobs are no longer bound to a deployment. The batch also no longer deletes versions of one process in parallel, which could leave a start timer or message subscription on a deleted version: they are deleted one after another, newest first (since 2.2.5)
  • Fixed deleting several versions of one process at the same time, e.g. with parallel calls of RepositoryService#deleteDeployment, leaving the start timer and the message start event subscription on a deleted version: deleting deployments and process definitions now takes the deployment lock (deploymentLockUsed), which the engine now also acquires on H2 2.x
  • Creating an attachment for a completed process instance no longer fails with HTTP 500, and attachments of completed tasks and process instances now get the removal time, so the history cleanup removes them (since 2.2.5)
  • Unknown task, process instance or attachment ids now fail with a clear error instead of an IndexOutOfBoundsException or NullPointerException (since 2.2.5)
  • Fixed the AI-output marker of the AI Agent Connector (agentOutput_aiMeta) not being readable when the engine’s default serialization format is JSON and type validation or Spin’s map type detector is on
  • Fixed expressions that call a method with null as the only argument of a varargs parameter failing with a NullPointerException; a method that cannot be accessed now fails with a MethodNotFoundException
  • Fixed list variables whose first element is null failing with a NullPointerException when serialized by Spin or the external task client
  • Fixed JavaScript script tasks leaking GraalJS polyglot contexts under sustained load (since 2.2.3)
  • Fixed the LDAP cache failing with NoClassDefFoundError on WildFly and Tomcat (since 2.2.2)
  • Fixed HistoricStatistics OR queries and the withoutTenantId flag in tenant queries (since 2.2.1)

REST API

  • Fixed POST /process-instance/delete and /process-instance/delete-historic-query-based rejecting "skipSubprocesses": null
  • Fixed object variables with java.util.Optional fields failing with HTTP 400 when fetched with deserializeValues=true
  • Fixed GET /variable-instance/{id}, /history/variable-instance/{id} and /history/detail/{id} (also their /data and DELETE) answering HTTP 500 on WildFly, which broke editing JSON variables in the webclient there (since 2.2.5)

External Task Client

  • Fixed the Spring Boot external task client starter ignoring the order-by-create-time and use-create-time properties

Spring Boot Starter and Database

  • With camunda.bpm.webapp.index-redirect-enabled=false, /webapp still forwards to its index.html instead of answering 404
  • Migrating a Camunda 7 database to CIB seven with the Liquibase changelog no longer tries to create the schema again; a schema older than Camunda 7.16 is rejected with a message

History Time To Live

  • Fixed “Unlimited” history time to live being saved as 0, so the history was removed by the next cleanup, and a definition without a time to live being shown with the engine default
  • Deploying a model without a history time to live on an engine that enforces one reports the missing value

Process Definitions and Instances

  • Fixed updating a task, e.g. its due date, resetting its priority
  • Fixed runtime process instances not being shown with history level none
  • Fixed the expand and collapse tooltips of the diagram viewer being swapped
  • Fixed the Incidents tab listing every incident twice when a second load, e.g. after sorting or searching, started before the first one had answered, and the Called process instances tab listing every called instance twice
  • Fixed the call activity link in the diagram being disabled when a process instance was opened directly, e.g. from the process instance search; it is enabled when the call activity started a called instance, and its tooltip names the reason when it is not
  • Fixed called process instances being empty with history level none (since 2.2.3), and the list of called process instances and definitions being incomplete (since 2.2.4)
  • Fixed the activity-scoped incidents list being empty for external task incidents (since 2.2.4)
  • Fixed historic activity statistics loading only on a specific tab, and the Variables tab depending on the history level (since 2.2.3)
  • Fixed deleting variables and stopping instances not following the engine’s permissions (since 2.2.4)
  • Fixed local variables with the same name showing identical values (since 2.2.2)
  • Fixed the wrong first and last started instance in the process definition details (since 2.2.2)
  • Fixed process definition versions not ordered descending, and the instance counter after deleting a version (since 2.2.1)

Decisions

  • Fixed every row of the Decisions list opening the same definition when a decision key is deployed for several tenants, or for a tenant and without one; the list, the version history, the instances and their links keep the tenant (?tenantId=), and GET services/v1/decision/key/{key}/versions takes the optional parameters tenantId and withoutTenantId=true; without them, it lists the versions of all tenants as before
  • Fixed the decision instance view marking rules that did not fire by comparing output texts; it now marks the rules that fired from their rule id
  • Fixed the batch operation criterion “Decision Definition Key In” with several values finding nothing
  • Fixed evaluating a decision, fetching its DMN XML by key, and evaluating by key and tenant through the default provider

Tasklist

  • Fixed task filter date criteria (e.g. dueAfter) being stored in an unsupported format that never matched
  • Fixed the task list searching endlessly when there is no filter
  • Fixed filters with comma-separated candidate groups failing, and the filter counter counting tasks the list then hid (since 2.2.4)
  • Fixed the task filter fetching more variables than configured, and scrolling to a task outside the current results (since 2.2.3)
  • Fixed the filter count not updating after completing a task, descending sorting with a due date filter, and paging after a filter change (since 2.2.2)
  • Tasks of inactive process instances are no longer shown, and the search field accepts more than 50 characters (since 2.2.1)

Admin

  • Fixed an unknown tenant answering 500 and leaving the Tenant page blank; an unknown group breaking the group page; and switching users in the URL of the account page
  • Fixed the account menu link being shown to users who may not open the account page
  • Fixed the permission selector, deleting and editing authorizations, and the response after creating one (since 2.2.1)

Direct Provider

  • Fixed user queries ignoring idIn, sorted user and group queries failing, and decision queries ignoring sorting, lazyLoad and paging
  • Fixed the historic batch search with tenantIdIn and suspending a batch
  • Fixed the first-run setup check answering 500 on Tomcat and WildFly; the setup refuses an empty password and, as with the default provider, is offered only while the engine is not configured yet
  • Fixed script tasks and expressions failing with HTTP 500 (“Could not find option with name js.syntax-extensions” or “Access to host class org.cibseven.spin.Spin is not allowed”) on WildFly; if the first script after a server start ran this way, JavaScript stayed broken for the whole server until a restart (since 2.2.5)
  • Fixed setting an execution-local variable storing it on the process instance, and unknown variables or process instances answering 500 instead of 404
  • Fixed decisions deployed for a tenant not opening in the Decisions view
  • Fixed JSON and object form values not being serialized when a form is submitted
  • Fixed paging of incident and external task queries, the runtime process instance count, the user operation log without authorization, and stopping process instances (since 2.2.4)
  • Fixed variable enrichment in task filters and the media type of deployed forms (since 2.2.2); authorization checks (since 2.2.1)
  • With the Direct Provider on CIB seven Run, engine calls no longer join the webclient’s own transaction: they commit on their own, as on Tomcat, on WildFly and with the REST provider, so a request can hold two pooled database connections at once. This fixes saving, updating and deleting modeler models failing with “Pre-bound JDBC Connection found!”

Webclient Backend

  • Fixed GET services/v1/process-history/instance/by-process-id/{id} with an empty text returning only the process instances that have a business key
  • Fixed a replaced logo, favicon or translation file not reaching the browser until its cache was cleared
  • Fixed pooled connections to the engine REST API failing with NoHttpResponseException when the server closes a connection
  • Fixed non-ASCII text and generated forms from the engine being decoded incorrectly
  • Fixed LdapUserProvider not closing LDAP contexts, and a duplicate PropertySourcesPlaceholderConfigurer bean (since 2.2.4)
  • Webclient dates are serialized as ISO-8601 strings (since 2.2.2)
  • Fixed multi-engine lookup, the redirect after login during an engine switch (since 2.2.2), and routing of rendered forms in a multi-engine setup (since 2.2.1)
  • Fixed deployed start and task forms, rendered forms and variable downloads forwarding the engine’s connection headers, so with the REST provider, a strict reverse proxy (e.g. NGINX) answered 502 for forms and files larger than about 8 KB because of a duplicate Transfer-Encoding header; they now pass on only Content-Type, Content-Disposition and Cache-Control, and Content-Encoding for binary content
  • New services/v1/process-definition/key/{key}/form-variables reads the start form variables of a definition key, with or without variableNames; services/v1/process-definition/{id}/form-variables with variableNames answered 500 for a key and keeps expecting a definition id

Forms

  • Fixed the SDK of embedded forms answering 404 or 405 when writing task-local or process variables (task.modifyVariables, task.localVariable, task.deleteVariable, process-instance.setVariable), with both providers
  • Fixed embedded forms: bpmnEscalation support and SDK user, group and history calls (since 2.2.2); error handling for embedded and deployed forms (since 2.2.1)

Modeler

  • Fixed Deploy and start failing for diagrams with pools and a double click deploying twice
  • Fixed deploying as the current user being disabled after a login without Remember me
  • Fixed the import counting failed files as imported, Replace marking a tab as saved after a failed update, and Rename of a diagram with a collaboration producing duplicate ids
  • Process keys are checked against the XML id rules, so Process_1 is accepted and keys with spaces or : are refused
  • Fixed the reason of a failed deployment not being shown
  • Fixed Start process in the deploy dialog failing, or starting another definition with the same key, after a deployment with a tenant ID
  • A wrong password when deploying as another user no longer logs the user out of the webclient, and a failed deployment or start shows only the modeler’s message
  • Fixed the form editor’s properties panel not updating, the sub-process breadcrumbs being covered by the palette, and sorting of table columns with empty cells
  • Fixed editor instances and listeners not being released on tab close, save and edit-lock failures being dropped, and element template handling when the modeler backend is disabled (since 2.2.2)
  • Stability fixes for tabs, imports, templates, the Properties Panel and the DMN editor (since 2.2.1)

Element Templates

  • The element template API answers 404 for unknown ids, lists unknown ids of a bulk delete as failed, refuses a taken template id, and keeps the active flag

Helm

  • Fixed overrides of config.json through the Helm chart having no effect

Technical Updates

Dependency Updates

  • Update Spring Boot from 3.5.14 to 4.1.2 (and spring-boot-4 from 4.0.6); Spring Boot 3 is no longer supported
  • Update Spring Framework to 7.0.10 (cibseven-engine-spring from 5.3.39)
  • Update log4j from 2.25.4 to 2.25.5
  • Update jackson from 2.21.2 to 2.21.7
  • Update jackson 3 (tools.jackson) from 3.1.2 to 3.1.7; now used by the engine REST API, Spin, the external task client and the webclient
  • Update tomcat from 11.0.22 to 11.0.27; tomcat9 and tomcat10 are no longer shipped
  • Update wildfly from 40.0.0.Final to 42.0.0.Final
  • Update wildfly.core from 32.0.0.Final to 34.0.0.Final
  • Update resteasy from 6.2.8.Final to 7.0.5.Final
  • Update jersey to 4.0.2
  • Update graal.js from 21.3.12 to 25.0.1
  • Update feel-engine from 1.19.3 to 1.19.6, fixing GHSA-vx3p-v6cf-vfjw
  • Update slf4j-api from 1.7.26 to 2.0.18
  • Update logback from 1.2.13 to 1.5.38
  • Update httpclient5 from 5.5 to 5.6.4 and httpcore5 from 5.3.4 to 5.4.3
  • Update postgresql (JDBC driver) from 42.7.11 to 42.7.13
  • Update quarkus from 3.27.0 to 3.33.3
  • Update freemarker from 2.3.31 to 2.3.35
  • Update gson from 2.8.9 to 2.13.2
  • Update langchain4j from 1.14.1 to 1.16.3 (langchain4j-pgvector from 1.14.1-beta24 to 1.16.3-beta26)
  • Update Jakarta EE from 10.0.0 to 11.0.0 and jakarta.el-api to 6.0.1
  • Update expressly to 6.0.0 (new runtime dependency of cibseven-engine-dmn)
  • Update angus-activation to 2.0.2 (new runtime dependency of cibseven-commons-typed-values)
  • Update json-path from 2.9.0 to 3.0.0 and json-smart from 2.5.2 to 2.6.0
  • Update cibseven-mcp-restapi to 0.0.6 (new in CIB seven Run)
  • Update springdoc-openapi from 2.8.13 (Spring Boot 3) and 3.0.2 (Spring Boot 4) to 3.1.0
  • Update swagger-ui from 5.32.6 to 5.34.1 (DOMPurify 3.4.17)
  • Replace jjwt-jackson with jjwt-gson 0.12.6
  • Update vue from 3.5.33 to 3.5.42
  • Update vue-i18n from 11.4.0 to 11.4.14
  • Update vite from 6.4.2 to 6.4.5
  • Update rollup from 4.60.3 to 4.62.5
  • Update axios from 1.15.2 to 1.20.0
  • Update moment from 2.30.1 to 2.31.0
  • Update dompurify from 3.4.2 to 3.4.17
  • Update @cib/bootstrap-components from 1.0.3 to 1.1.0
  • Update @cib/common-frontend from 1.0.3 to 1.1.0
  • Update @cib/bootstrap-theme from 1.0.1 to 1.1.0
  • Update bpm-sdk from 2.1.2 to 2.1.4
  • Update cibseven-modeler from 1.0.0 to 1.3.0
  • Update cibseven-modeler-ee from 1.0.0 to 1.3.0 (EE exclusive)
  • Update cibseven-bpmn-agent from 1.0.0 to 1.1.0 (EE exclusive)
  • Update cibseven-agent-chat-ui from 1.0.0 to 1.1.0 (EE exclusive)
  • Update OpenTelemetry Java agent (Docker images) from 2.26.1 to 2.28.1
  • Update openssl (libcrypto3, libssl3) from 3.5.6-r0 to the current Alpine 3.23 package (3.5.9-r0 or later); the images no longer pin the version (Alpine base image)
  • Update zlib from 1.3.1-r2 to 1.4-r0 (Alpine base image), fixing CVE-2026-4738
  • Update musl from 1.2.5-r23 to 1.2.5-r24 (Alpine base image)
  • Update curl (libcurl) from 8.19.0-r0 to 8.23.0-r0 (Alpine base image)
  • Update c-ares from 1.34.6-r0 to 1.34.8-r0 (Alpine base image)
  • Update brotli-libs from 1.2.0-r0 to 1.2.1-r0 (Alpine base image)
  • Update libxslt from 1.1.43-r3 to 1.1.43-r4 (Alpine base image)
  • Update ca-certificates to 20261020 (Alpine base image), which no longer trusts emSign ECC Root CA - G3
  • Update the Java runtime (openjdk21-jre-headless) to 21.0.13.1 (Alpine base image), which blocks the compromised eMudhra intermediate CA certificates and fixes CVE-2026-114938 (Java4Shell)
  • Update guava to 33.7.2 and snappy-java to 1.1.10.9 (WildFly distribution)

Resolved CVE Vulnerabilities

Critical Severity
  • CVE-2026-111497 - Buffer overflow in the Brotli decoder (versions 1.0.3 through 1.2.0) lets a remote unauthenticated attacker corrupt decoder memory, disclose memory contents, cause a Denial of Service or potentially execute code. Affects brotli-libs. - CVSS 8.1. (since 2.2.5)

  • CVE-2026-114820 - Critical vulnerability in the Java runtime of the Docker images, resolved by the Java runtime update. Affects openjdk21-jre-headless. (since 2.2.4 hotfix)

  • CVE-2026-46470 - Critical vulnerability in the Java runtime of the Docker images, resolved by the Java runtime update. Affects openjdk21-jre-headless. (since 2.2.4 hotfix)

  • CVE-2026-47884 - Use of XsltView in a Spring MVC application can lead to SSRF and remote code execution if the application has a /** mapping that renders a view whose name is not specified explicitly. Affects org.springframework:spring-webmvc. - CVSS 9.8.

  • CVE-2026-47890 - Spring MVC and WebFlux applications are vulnerable to stream corruption when using Server-Sent Events (SSE) with view fragments. Affects org.springframework:spring-webmvc. - CVSS 9.8.

  • CVE-2026-91403 - eMudhra generated weak private keys for 8 intermediate CAs, so TLS certificates that chain to them can be forged. This exposes outbound TLS connections from the container that use the default Java truststore, e.g. the AI Agent Connector, the HTTP connector, OIDC/JWKS or mail. Affects the Java truststore (openjdk, ca-certificates). - CVSS 9.1. (since 2.2.4 hotfix)

  • CVE-2026-65182 - Improper Access Control, Incorrect Authorization vulnerability in Apache Tomcat leads to security constraint bypass if a constraint for a longer path is specified before a more restrictive constraint for a shorter sub-path. Affects org.apache.tomcat.embed:tomcat-embed-core, org.apache.tomcat:tomcat-catalina. - CVSS 9.1. (since 2.2.3)

  • CVE-2026-65905 - Authentication Bypass by Capture-replay vulnerability in Apache Tomcat’s DIGEST authenticator. Affects org.apache.tomcat.embed:tomcat-embed-core, org.apache.tomcat:tomcat-catalina. - CVSS 9.8. (since 2.2.3)

  • CVE-2026-68525 - Incorrect Authorization vulnerability in Apache Tomcat’s FORM authentication process allows the bypassing of a security constraint that limits user has access to a resource POST but not GET. Affects org.apache.tomcat.embed:tomcat-embed-core, org.apache.tomcat:tomcat-catalina. - CVSS 9.1. (since 2.2.3)

  • CVE-2026-84939 - Path traversal in Apache FreeMarker’s template loading when an attacker can supply a malformed locale identifier and localized lookup is enabled, which it is by default. Affects org.freemarker:freemarker. - CVSS 9.1. (since 2.2.4)

  • CVE-2026-76183 - Authentication bypass by alternate name in Apache Tomcat lets an attacker bypass the security constraints of WebSocket endpoints (Camunda Security Notice 171). CIB seven itself has no WebSocket endpoints; applications deployed into the Tomcat distribution that use them are affected. Fixed by Tomcat 11.0.27, 10.1.61 and 9.0.123. Affects org.apache.tomcat. - CVSS 9.8. (since 2.2.5)

  • GHSA-cg2g-xh64-v4q7 - Sanitizer bypass in DOMPurify 3.4.4 to 3.4.16, bundled with the Swagger UI of the webclient and CIB seven Run. The Swagger UI does not use the affected DOMPurify options. Affects org.webjars:swagger-ui (dompurify). (since 2.2.5)

  • GHSA-vx3p-v6cf-vfjw - External Java functions in FEEL expressions could be called although the DMN engine disables them, when a function definition was passed as an argument of a function invocation, e.g. to sort(). Affects org.camunda.feel:feel-engine. - CVSS 9.9.

  • CVE-2026-55276 - Apache Tomcat leaves special roles and empty authorization constraints out when it logs the effective web.xml, which misleads the review of security constraints. Affects org.apache.tomcat.embed:tomcat-embed-core, org.apache.tomcat:tomcat-util-scan. - CVSS 2.3.

  • CVE-2026-65637 - Improper input validation in Apache Tomcat, caused by an incomplete fix for CVE-2026-32990. Affects org.apache.tomcat.embed:tomcat-embed-core, org.apache.tomcat:tomcat-coyote. - CVSS 9.8.

High Severity
  • CVE-2026-102554 - Unbounded allocation during Java object deserialization in Google Guava (4.0 through 33.7.1) allows a Denial of Service via OutOfMemoryError. Affects com.google.guava:guava (WildFly distribution). - CVSS 5.9. (since 2.2.5)

  • CVE-2026-107891 - Vulnerability in musl libc, fixed in 1.2.5-r24 (Alpine base image). Affects musl, musl-utils. (since 2.2.5)

  • CVE-2026-108106 - Unbounded memory allocation in snappy-java before 1.1.10.9 lets an attacker exhaust JVM memory by declaring a large uncompressed length in compressed input. Affects org.xerial.snappy:snappy-java (WildFly distribution). - CVSS 7.5. (since 2.2.5)

  • CVE-2026-125350 - Use after free in the XML processing of libxslt, which allowed a crafted HTML page to execute code inside the Google Chrome sandbox. Affects libxslt. (since 2.2.5)

  • CVE-2026-6732 - A malicious document can trigger a type confusion error that crashes the application. Affects openjdk21-jre-headless. - CVSS 7.5. (since 2.2.5)

  • CVE-2026-87636 - Type confusion in the XML processing of libxslt, which allowed a crafted HTML page to execute code inside the Google Chrome sandbox. Affects libxslt. - CVSS 8.8. (since 2.2.5)

  • CVE-2026-92392 - During an upload, curl mishandles HTTP/2 RST_STREAM received from the server (with reason HTTP_1_1_REQUIRED or REFUSED_STREAM) leading to a use after free of a struct Curl_easy object. Affects libcurl, curl. - CVSS 8.1. (since 2.2.5)

  • CVE-2026-93451 - Buffer overflow in the typed Snappy.uncompress*Array methods of snappy-java through 1.1.10.8, which pass the undivided uncompressed length to native code. Affects org.xerial.snappy:snappy-java (WildFly distribution). - CVSS 7.5. (since 2.2.5)

  • CVE-2026-9947 - Use after free in the XML processing of libxslt, which allowed a crafted HTML page to execute code inside the Google Chrome sandbox. Affects libxslt. - CVSS 9.6. (since 2.2.5)

  • CVE-2026-45447 - Use-after-free in openssl (libcrypto3, libssl3) during PKCS#7 signature verification when processing a signed message with an empty digestAlgorithms SET, potentially enabling heap corruption or remote code execution. Fixed in 3.5.7-r0 (Alpine base image). (since 2.2.1)

  • CVE-2026-54512 - Vulnerability in com.fasterxml.jackson.core:jackson-databind 2.21.2, fixed by upgrading to 2.21.4. (since 2.2.1)

  • CVE-2026-54513 - Vulnerability in com.fasterxml.jackson.core:jackson-core 2.21.2, fixed by upgrading to 2.21.4. (since 2.2.1)

  • CVE-2026-55405 - SQL injection in dev.langchain4j:langchain4j-pgvector via unescaped metadata filter keys in EmbeddingSearchRequest.filter(), enabling blind data exfiltration or row deletion when attacker-controlled filter keys reach the embedding store. Fixed in 1.16.3-beta26. (since 2.2.1)

  • CVE-2026-44249 - IPv6 subnet rule bypass in io.netty:netty-handler IpSubnetFilterRule due to incorrect masking, allowing public IPs to bypass access controls. Fixed in netty 4.1.135.Final (WildFly distribution). (since 2.2.1)

  • CVE-2026-45416 - Unbounded heap allocation in io.netty:netty-handler SslClientHelloHandler for oversized TLS ClientHello messages when SniHandler constructors disable the length guard and timeout. Fixed in netty 4.1.135.Final (WildFly distribution). (since 2.2.1)

  • CVE-2026-45674 - DNS cache poisoning via CNAME bailiwick bypass in io.netty:netty-resolver-dns, allowing a compromised authoritative server to inject records for parent domains. Fixed in netty 4.1.135.Final (WildFly distribution). (since 2.2.1)

  • CVE-2026-47691 - DNS cache poisoning via NS bailiwick bypass in io.netty:netty-resolver-dns, allowing a subdomain-authoritative server to poison the cache for parent zones. Fixed in netty 4.1.135.Final (WildFly distribution). (since 2.2.1)

  • CVE-2025-59250 - Improper input validation in the JDBC Driver for SQL Server allows an unauthorized attacker to perform spoofing over a network. Affects com.microsoft.sqlserver:mssql-jdbc. - CVSS 8.1. (since 2.2.2)

  • CVE-2026-33630 - Vulnerability fixed by upgrading the affected package. Affects c-ares. (since 2.2.2)

  • CVE-2026-40983 - Specially crafted gRPC requests to Micrometer may cause a denial-of-service condition. Affects io.micrometer:micrometer-core. - CVSS 7.5. (since 2.2.2)

  • CVE-2026-40984 - Specially crafted HTTP requests to Micrometer may cause a denial-of-service condition. Affects io.micrometer:micrometer-core. - CVSS 7.5. (since 2.2.2)

  • CVE-2026-41254 - Little CMS (lcms2) through 2.18 has an integer overflow in CubeSize in cmslut.c because the overflow check is performed after the multiplication. Affects openjdk21-jre-headless. - CVSS 7.5. (since 2.2.2)

  • CVE-2026-47063 - Easily exploitable vulnerability allows an unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 7.5. (since 2.2.2)

  • CVE-2026-50645 - No restriction on the number of attachment headers a message can contain when deserialized by Apache CXF can lead to uncontrolled resource consumption or a denial of service attack. Affects org.apache.cxf:cxf-core. - CVSS 7.5. (since 2.2.2)

  • CVE-2026-54291 - Channel-binding downgrade vulnerability in pgjdbc, allowing an on-path attacker to bypass SCRAM channel binding on the AI agent’s PostgreSQL connector. Affects org.postgresql:postgresql. - CVSS 5.9. (since 2.2.2)

  • CVE-2026-55831 - Netty’s SPDY SETTINGS decoder accepts a peer-declared entry count up to the 24-bit frame-length limit, allowing a remote SPDY/3.1 peer to send an oversized SETTINGS frame that exhausts memory. Affects io.netty:netty-codec-http. - CVSS 7.5. (since 2.2.2)

  • CVE-2026-55833 - Netty SPDY header decoding continues inflating zlib-compressed header blocks after the parser has exceeded maxHeaderSize, letting a small compressed block expand into much larger memory use. Affects io.netty:netty-codec-http. - CVSS 7.5. (since 2.2.2)

  • CVE-2026-56745 - Vulnerability in Netty’s codec-http module, fixed in 4.1.136.Final and 4.2.16.Final. Affects io.netty:netty-codec-http. (since 2.2.2)

  • CVE-2026-56819 - A remote unauthenticated peer can leak one direct ByteBuf per HTTP/2 DATA frame in applications that enable HTTP/2 content decompression via DelegatingDecompressorFrameListener. Affects io.netty:netty-codec-http2. - CVSS 7.5. (since 2.2.2)

  • CVE-2026-5773 - A logical error in the connection reuse mechanism for SMB transfers could lead libcurl to reuse an existing SMB connection with a different share than intended. Affects curl, libcurl. - CVSS 6.5. (since 2.2.2)

  • CVE-2026-59901 - The Bzip2Decoder handler in Netty’s compression codec pipeline is vulnerable to a denial-of-service attack via a malformed bzip2 stream that permanently captures the event-loop thread in an infinite loop. Affects io.netty:netty-codec. (since 2.2.2)

  • CVE-2026-62574 - Easily exploitable vulnerability allows a low-privileged attacker with logon access to the infrastructure to compromise Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 7.8. (since 2.2.2)

  • CVE-2026-6276 - A custom Host: header used in an initial HTTP request could leak to a second host when the connection is reused without a new Host: header, resulting in a cookie leak. Affects curl, libcurl. - CVSS 3.7. (since 2.2.2)

  • CVE-2026-11352 - An issue in curl’s QUIC UDP receive function allows a malicious HTTP/3 server to trigger a remote denial of service against a curl or libcurl client. Affects curl, libcurl. - CVSS 7.5. (since 2.2.3)

  • CVE-2026-11586 - By default, curl automatically responds to WebSocket PING frames. Affects curl, libcurl. - CVSS 7.5. (since 2.2.3)

  • CVE-2026-12064 - When a user invokes curl using a schemeless URL combined with --proto-default sftp (or scp), a disconnect occurs between the tool layer and libcurl. Affects curl, libcurl. - CVSS 7.5. (since 2.2.3)

  • CVE-2026-14456 - Impact summary: A remote peer that can make many Initial packets reach the server listener faster than the application accepts connections, can cause the memory allocated to store the per-channel state to grow without any limits, potentially making the QUIC listener unavailable and causing Denial of Service. Affects libcrypto3, libssl3. - CVSS 7.5. (since 2.2.3)

  • CVE-2026-54399 - Uncontrolled Resource Consumption vulnerability in the HTTP/1.1 message parser in Apache HttpComponents Core (5.4.2 and earlier, 5.5-beta1 and earlier) allows an remote attacker to cause a denial of service through memory exhaustion by sending messages with excessive number of headers / excessive header length. Affects org.apache.httpcomponents.core5:httpcore5. - CVSS 7.5. (since 2.2.3)

  • CVE-2026-54428 - Allocation of resources without limits in the HTTP/2 HPACK decoder of Apache HttpComponents Core (5.4.2 and earlier) allows a remote attacker to cause a Denial of Service through memory exhaustion by sending oversized compressed header blocks. Affects org.apache.httpcomponents.core5:httpcore5-h2. - CVSS 7.5. (since 2.2.3)

  • CVE-2026-8286 - A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not. Affects curl, libcurl. - CVSS 8.1. (since 2.2.3)

  • CVE-2026-8458 - libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different ‘services’. Affects curl, libcurl. - CVSS 6.5. (since 2.2.3)

  • CVE-2026-8925 - The curl logic that works with SASL authentication could end up cleaning up the GSASL context twice without clearing the pointer in between, making it free() the same pointer twice. Affects curl, libcurl. - CVSS 9.8. (since 2.2.3)

  • CVE-2026-8927 - When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Affects curl, libcurl. - CVSS 9.1. (since 2.2.3)

  • CVE-2026-9547 - When a libcurl-based application performs transfers via SCP:// or SFTP:// and utilizes the CURLOPT_SSH_KEYFUNCTION callback, it may silently accept an untrusted server. Affects curl, libcurl. - CVSS 7.4. (since 2.2.3)

  • CVE-2026-106451 - Vulnerability in lz4-java fixed in version 1.11.4. Affects at.yawk.lz4:lz4-java. - CVSS 7.0. (since 2.2.4)

  • CVE-2026-68497 - An unauthenticated attacker can send a request of a few megabytes with an oversized Duration value (e.g. P followed by several million digits and Y) to force tens of seconds to several minutes of single-threaded CPU work per request, so a handful of concurrent requests can saturate the server. Affects com.fasterxml.jackson.core:jackson-databind. - CVSS 7.5. (since 2.2.4)

  • CVE-2026-77226 - Incorrect authorization in the first-run setup (Camunda Security Notice 171): on an engine that was already administered but had an empty or missing camunda-admin group, an unauthenticated attacker could create a new administrator account, leading to account takeover. Affects the Admin web application and the engine REST setup endpoint. - CVSS 8.1. (since 2.2.4)

  • CVE-2026-85091 - Heap buffer overflow in gz_vacate() when processing non-blocking gzwrite() operations with stale external buffer pointers (zlib 1.3.1.2 through 1.3.2). Affects zlib. (since 2.2.4)

  • CVE-2026-89407 - Attacker-supplied JSON deserialized into a numeric type (BigDecimal, BigInteger, Double, Float) reaches a vulnerable number-parsing method through jackson-databind’s default String-to-number coercion. Affects com.fasterxml.jackson.core:jackson-core. - CVSS 7.5. (since 2.2.4)

  • CVE-2026-89425 - UTF8DataInputJsonParser._reportInvalidToken() builds the offending-token text for its error message in a loop with no upper bound. Affects com.fasterxml.jackson.core:jackson-core. - CVSS 7.5. (since 2.2.4)

  • CVE-2026-91776 - TypeDeserializerBase._findDeserializer() caches resolved deserializers under the raw, attacker-supplied type ID. Affects com.fasterxml.jackson.core:jackson-databind. - CVSS 7.5. (since 2.2.4)

  • CVE-2026-91777 - Vulnerability exploitable when an application deserializes attacker-influenced JSON into an identity-enabled collection or map. Affects com.fasterxml.jackson.core:jackson-databind. - CVSS 7.5. (since 2.2.4)

  • CVE-2026-109431 - Missing authorization checks let authenticated users without any permission read, download or delete the attachments and read the comments of tasks and process instances, knowing only their id. Affects the process engine and the engine REST API. - CVSS 7.3. (since 2.2.5)

  • CVE-2026-114938 - “Java4Shell”: heap out-of-bounds write in the HotSpot C2 intrinsic of the java.util.Base64 decoder on x86-64 CPUs with AVX-512 VBMI (Intel Ice Lake, AMD Zen 4 and newer), so a JVM that decodes attacker-controlled Base64 can be made to corrupt heap memory, up to remote code execution. The webclient decodes the Authorization header and JWT payloads before login. Affects openjdk21-jre-headless. - CVSS 8.1. (since 2.2.5)

  • CVE-2026-77224 - XML external entity (XXE) injection in the Java External Task Client: a user who may set a process variable can make a worker that deserializes an application/xml object variable read local files and send requests to other hosts. Affects org.cibseven.bpm:cibseven-external-task-client. - CVSS 7.5. (since 2.2.5)

  • GHSA-mrv2-3pqr-j5jr - Sanitizer bypass in DOMPurify up to 3.4.16, bundled with the Swagger UI of the webclient and CIB seven Run. The Swagger UI does not use the affected DOMPurify options. Affects org.webjars:swagger-ui (dompurify). (since 2.2.5)

  • CVE-2026-114939 - Vulnerability in the Java runtime that an unauthenticated attacker with network access can exploit, though with difficulty. Affects openjdk21-jre-headless. - CVSS 7.4. (since 2.2.5)

  • CVE-2026-114940 - Vulnerability in the Java runtime that an unauthenticated attacker with network access via TLS can exploit, though with difficulty. Affects openjdk21-jre-headless. - CVSS 7.4. (since 2.2.5)

  • CVE-2026-114941 - Vulnerability in the Java runtime that an unauthenticated attacker with network access can exploit, though with difficulty. Affects openjdk21-jre-headless. - CVSS 7.0. (since 2.2.5)

  • CVE-2026-114942 - Vulnerability in the Java runtime that an unauthenticated attacker with network access can exploit, though with difficulty. Affects openjdk21-jre-headless. - CVSS 7.0. (since 2.2.5)

  • CVE-2026-53404 - Apache Tomcat’s rewrite valve skips the following non-OR conditions when the first condition of an OR chain matches. Affects org.apache.tomcat.embed:tomcat-embed-core, org.apache.tomcat:tomcat-catalina. - CVSS 7.3.

Medium Severity
  • CVE-2025-10911 - A use-after-free vulnerability was found in libxslt while parsing xsl nodes that may lead to the dereference of expired pointers and application crash. Affects libxslt. - CVSS 5.5. (since 2.2.5)

  • CVE-2026-116590 - Snappy.arrayCopy in snappy-java before 1.1.10.9 passes unvalidated ranges to native memcpy, allowing reads or writes outside array bounds that crash the JVM. Affects org.xerial.snappy:snappy-java (WildFly distribution). - CVSS 5.9. (since 2.2.5)

  • CVE-2026-83374 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 5.9. (since 2.2.5)

  • CVE-2026-83378 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE. Affects openjdk21-jre-headless. - CVSS 3.7. (since 2.2.5)

  • CVE-2026-83381 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE. Affects openjdk21-jre-headless. - CVSS 4.8. (since 2.2.5)

  • CVE-2026-83387 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 5.9. (since 2.2.5)

  • CVE-2026-83400 - Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 5.3. (since 2.2.5)

  • CVE-2026-87290 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 3.7. (since 2.2.5)

  • CVE-2026-87291 - Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE. Affects openjdk21-jre-headless. - CVSS 5.3. (since 2.2.5)

  • CVE-2026-91332 - Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE. Affects openjdk21-jre-headless. - CVSS 5.3. (since 2.2.5)

  • CVE-2026-91373 - Easily exploitable vulnerability allows unauthenticated attacker with network access via TLS to compromise Oracle Java SE. Affects openjdk21-jre-headless. - CVSS 5.3. (since 2.2.5)

  • CVE-2026-91374 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 4.8. (since 2.2.5)

  • CVE-2026-91375 - Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Oracle Java SE executes to compromise Oracle Java SE. Affects openjdk21-jre-headless. - CVSS 4.7. (since 2.2.5)

  • CVE-2026-91379 - Difficult to exploit vulnerability allows an unauthenticated attacker with logon to the infrastructure to compromise Oracle Java SE, Oracle GraalVM for JDK and Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 4.7. (since 2.2.5)

  • CVE-2026-91417 - Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 5.3. (since 2.2.5)

  • CVE-2026-91418 - Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle JavaFX, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 5.3. (since 2.2.5)

  • CVE-2026-91451 - Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE. Affects openjdk21-jre-headless. - CVSS 5.3. (since 2.2.5)

  • CVE-2026-91452 - Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 5.3. (since 2.2.5)

  • CVE-2026-91453 - Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 5.3. (since 2.2.5)

  • CVE-2026-91462 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 5.9. (since 2.2.5)

  • CVE-2026-91463 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 5.3. (since 2.2.5)

  • CVE-2026-91464 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 5.3. (since 2.2.5)

  • CVE-2026-91487 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE. Affects openjdk21-jre-headless. - CVSS 4.8. (since 2.2.5)

  • CVE-2026-92388 - After a failed FTP wildcard LIST operation, libcurl leaves the internal listing parser installed as write callback, pointing directly to the easy handle. Affects libcurl, curl. - CVSS 6.5. (since 2.2.5)

  • CVE-2026-34182 - Insufficient validation of cipher and tag length fields in openssl CMS AuthEnvelopedData processing, allowing an on-path attacker to achieve key-equivalent functionality or bypass integrity validation. Fixed in openssl 3.5.7-r0 (Alpine base image). (since 2.2.1)

  • CVE-2026-34183 - Unbounded memory allocation in openssl QUIC stack via malicious PATH_CHALLENGE frames, leading to Denial of Service. Fixed in openssl 3.5.7-r0 (Alpine base image). (since 2.2.1)

  • CVE-2026-42764 - NULL pointer dereference in openssl QUIC server when receiving an initial packet with an invalid token and address validation disabled, causing Denial of Service. Fixed in openssl 3.5.7-r0 (Alpine base image). (since 2.2.1)

  • CVE-2026-45445 - Application-supplied IV silently discarded in openssl AES-OCB via EVP_Cipher() one-shot interface, causing nonce reuse, loss of confidentiality, and universal authentication tag forgery. Fixed in openssl 3.5.7-r0 (Alpine base image). (since 2.2.1)

  • CVE-2026-45536 - File descriptor leak in io.netty:netty-transport-native-epoll when a peer sends a SCM_RIGHTS cmsg carrying two file descriptors, bypassing the single-fd check. Fixed in netty 4.1.135.Final (WildFly distribution). (since 2.2.1)

  • CVE-2026-45673 - DNS cache poisoning via predictable transaction IDs and static UDP source port in io.netty:netty-resolver-dns, reducing entropy for Kaminsky-style attacks. Fixed in netty 4.1.135.Final (WildFly distribution). (since 2.2.1)

  • CVE-2026-47244 - No default SETTINGS_MAX_CONCURRENT_STREAMS enforcement in io.netty:netty-codec-http2, allowing a single connection to open an unbounded number of streams and cause Denial of Service. Fixed in netty 4.1.135.Final (WildFly distribution). (since 2.2.1)

  • CVE-2026-40914 - An application using the STOMP protocol with credentials granting only consume or send permission on an address could augment that address’s routing type without the createAddress permission. Affects org.apache.artemis:artemis-stomp-protocol. - CVSS 4.3. (since 2.2.2)

  • CVE-2026-46917 - Easily exploitable vulnerability allows an unauthenticated attacker with network access via TLS to compromise Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 5.3. (since 2.2.2)

  • CVE-2026-46968 - Difficult to exploit vulnerability allows an unauthenticated attacker with network access via TLS to compromise Oracle Java SE. Affects openjdk21-jre-headless. - CVSS 5.9. (since 2.2.2)

  • CVE-2026-47021 - Easily exploitable vulnerability allows an unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 5.3. (since 2.2.2)

  • CVE-2026-47027 - Easily exploitable vulnerability allows an unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE. Affects openjdk21-jre-headless. - CVSS 5.3. (since 2.2.2)

  • CVE-2026-4873 - An unencrypted connection followed by a subsequent request requiring TLS to the same host could bypass the TLS requirement due to incorrect connection reuse, leaking data in cleartext. Affects curl, libcurl. - CVSS 5.3. (since 2.2.2)

  • CVE-2026-54515 - Per-property @JsonIgnoreProperties exclusions combined with @JsonFormat(ACCEPT_CASE_INSENSITIVE_PROPERTIES) could restore properties that were meant to stay ignored, making them writable again. Affects com.fasterxml.jackson.core:jackson-databind. - CVSS 5.3. (since 2.2.2)

  • CVE-2026-54704 - The OpenTelemetry Java agent’s JDBC auto-instrumentation fails to sanitize double-quoted passwords in SQL CONNECT statements, allowing clear-text database passwords to be written to trace span attributes. Affects io.opentelemetry.javaagent:opentelemetry-javaagent. - CVSS 6.5. (since 2.2.2)

  • CVE-2026-54712 - Unbounded memory allocation in the OpenTelemetry Java agent’s RMI context propagation payload reader, which limits the number of context entries but not the aggregate size of the strings read from the stream. Affects io.opentelemetry.javaagent:opentelemetry-javaagent. - CVSS 7.5. (since 2.2.2)

  • CVE-2026-5545 - An authenticated HTTP(S) request following a Negotiate-authenticated one to the same host may incorrectly reuse the previous connection, letting the second request run under different credentials. Affects curl, libcurl. - CVSS 6.5. (since 2.2.2)

  • CVE-2026-56746 - Netty is vulnerable to a security control bypass during the origin evaluation process. Affects io.netty:netty-codec-http. - CVSS 6.5. (since 2.2.2)

  • CVE-2026-59889 - A property annotated with both @JsonView and @JsonUnwrapped could be written from attacker JSON under a less-privileged active view. Affects com.fasterxml.jackson.core:jackson-databind. - CVSS 6.5. (since 2.2.2)

  • CVE-2026-59898 - An attacker can force a WebSocket upgrade via the lax V07/V08 handshaker by omitting the Connection: Upgrade/Upgrade: websocket headers, enabling HTTP request smuggling. Affects io.netty:netty-codec-http. (since 2.2.2)

  • CVE-2026-59899 - HttpContentEncoder maintains a per-channel queue that accumulates attacker-controlled data without any size limit. Affects io.netty:netty-codec-http. (since 2.2.2)

  • CVE-2026-59900 - Netty’s HTTP/2-to-HTTP/1.x translation layer fails to deduplicate or validate Host headers when a client supplies both :authority and a literal host header. Affects io.netty:netty-codec-http2. (since 2.2.2)

  • CVE-2026-59921 - CRLF injection via a multipart filename in Netty’s HttpPostRequestEncoder allows an attacker to inject arbitrary MIME headers. Affects io.netty:netty-codec-http. - CVSS 5.7. (since 2.2.2)

  • CVE-2026-59949 - Insufficient validation of byte array arguments in JNI-based XXHash implementations allows callers to crash the JVM by passing an invalid array reference or range to native methods. Affects at.yawk.lz4:lz4-java. - CVSS 6.5. (since 2.2.2)

  • CVE-2026-60147 - Easily exploitable vulnerability allows an unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 6.5. (since 2.2.2)

  • CVE-2026-6253 - Redirecting from an authenticated proxy to an unauthenticated one when using distinct proxies per URL scheme could inadvertently expose the initial proxy’s credentials. Affects curl, libcurl. - CVSS 5.3. (since 2.2.2)

  • CVE-2026-6429 - Following an HTTP redirect while using a .netrc file for credentials could send the password from the initial connection to the redirected host. Affects curl, libcurl. - CVSS 6.5. (since 2.2.2)

  • CVE-2026-7009 - Vulnerability fixed by upgrading the affected package. Affects curl, libcurl. (since 2.2.2)

  • CVE-2026-7168 - Vulnerability fixed by upgrading the affected package. Affects curl, libcurl. (since 2.2.2)

  • GHSA-mfg7-5gfp-c4w3 - A memory leak can be caused in Netty’s DNS codec by sending malicious DNS packets containing invalid domain names. Affects io.netty:netty-codec-dns. - CVSS 5.3. (since 2.2.2)

  • GHSA-mhm7-754m-9p8w - A creator parameter annotated with both @JsonView(RestrictedView.class) and an external-type-id @JsonTypeInfo could be populated from attacker JSON even when a more restrictive view was active. Affects com.fasterxml.jackson.core:jackson-databind. - CVSS 6.5. (since 2.2.2)

  • CVE-2026-10536 - A use-after-free vulnerability exists in libcurl when an application configures an HTTP/2 stream-dependency tree via CURLOPT_STREAM_DEPENDS or CURLOPT_STREAM_DEPENDS_E, subsequently invokes curl_easy_reset(), and finally terminates the handle with curl_easy_cleanup(). Affects curl, libcurl. - CVSS 9.8. (since 2.2.3)

  • CVE-2026-11564 - libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. Affects curl, libcurl. - CVSS 6.5. (since 2.2.3)

  • CVE-2026-11856 - Successfully using libcurl to do a transfer to a specific HTTP origin (hostA) with Digest authentication and then changing the origin to a different one (hostB) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the Authorization: header field meant for hostA, to hostB. Affects curl, libcurl. - CVSS 9.8. (since 2.2.3)

  • CVE-2026-18798 - Impact summary: Double free leads to heap corruption, which typically results in termination of QUIC server process, leading to Denial of Service. Affects libcrypto3, libssl3. - CVSS 7.5. (since 2.2.3)

  • CVE-2026-49844 - * The application logs a MapMessage that contains an attacker-controlled floating-point value. Affects org.apache.logging.log4j:log4j-api. - CVSS 5.9. (since 2.2.3)

  • CVE-2026-59903 - Prior to 4.1.137.Final and 4.2.17.Final, io.netty.handler.codec.http.cors.CorsHandler setVaryHeader replaces application Vary headers such as Authorization or Cookie with Origin, allowing a caching proxy or CDN to reuse authenticated responses across users and disclose sensitive information. Affects io.netty:netty-codec-http. - CVSS 6.5. (since 2.2.3)

  • CVE-2026-63072 - Impact summary: An attacker who supplies a crafted CMS message can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service. Affects libcrypto3, libssl3. - CVSS 7.5. (since 2.2.3)

  • CVE-2026-63076 - Impact summary: A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a Denial of Service. Affects libcrypto3, libssl3. - CVSS 7.5. (since 2.2.3)

  • CVE-2026-64607 - HttpClient based on the classic i/o model fails to correctly release the underlying connection back to the connection manager if it encounters an invalid or unsupported Content-Encoding header value in the response message. Affects org.apache.httpcomponents.client5:httpclient5. - CVSS 5.3. (since 2.2.3)

  • CVE-2026-8924 - A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set ‘super cookies’ that bypass the Public Suffix List check. Affects curl, libcurl. - CVSS 9.1. (since 2.2.3)

  • CVE-2026-8926 - When curl uses a .netrc file and the URL names a user without a password, curl could use the password of another user stored in the .netrc file for that host. Affects curl, libcurl. - CVSS 9.1. (since 2.2.3)

  • CVE-2026-8932 - libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse. Affects curl, libcurl. - CVSS 7.5. (since 2.2.3)

  • CVE-2026-9079 - libcurl had a flaw that when instructed to clear proxy authentication credentials which made it not do so, leaving the old credentials around to get used for subsequent transfers that should not know nor use them. Affects curl, libcurl. - CVSS 9.8. (since 2.2.3)

  • CVE-2026-9080 - Calling curl_easy_pause() within the event-based CURLMOPT_SOCKETFUNCTION callback triggers a use-after-free vulnerability, where libcurl attempts to store a flag using a dangling struct pointer immediately after that pointer’s memory has been freed. Affects curl, libcurl. - CVSS 7.3. (since 2.2.3)

  • CVE-2026-9545 - In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker’s impostor machine - without a valid certificate. Affects curl, libcurl. - CVSS 7.5. (since 2.2.3)

  • CVE-2026-9546 - A vulnerability in libcurl caused the HTTP Referer: header to persist even when explicitly cleared. Affects curl, libcurl. - CVSS 7.5. (since 2.2.3)

  • CVE-2026-106450 - LZ4FrameInputStream.readHeader() allocates two new 4 MiB block buffers for every maximum-block-size frame header, so an attacker-controlled stream of many minimal empty frames triggers excessive memory allocation. Affects at.yawk.lz4:lz4-java. - CVSS 5.3. (since 2.2.4)

  • CVE-2026-106452 - LZ4BlockInputStream.refill() allocates a compressed-input buffer of the attacker-controlled size from a legacy block header before reading any payload, so a header-only stream can request a near-2 GiB allocation. Affects at.yawk.lz4:lz4-java. - CVSS 5.3. (since 2.2.4)

  • CVE-2026-106453 - LZ4DecompressorWithLength trusts the four-byte decompressed-length header before validating the compressed input, so a five-byte input can request up to approximately 2 GiB and exhaust the JVM heap. Affects at.yawk.lz4:lz4-java. - CVSS 5.3. (since 2.2.4)

  • CVE-2026-19032 - The deserializer for java.nio.file.Path resolves an attacker-supplied URI without restricting the URI scheme. Affects com.fasterxml.jackson.core:jackson-databind. - CVSS 5.3. (since 2.2.4)

  • CVE-2026-83557 - Attacker-controlled input can instantiate objects, e.g. a java.io.File for an arbitrary path, which becomes path-traversal-adjacent if the application then calls path-sensitive methods on the value. Affects com.fasterxml.jackson.core:jackson-databind. - CVSS 5.6. (since 2.2.4)

  • Camunda Security Notice 157 - Authenticated users could inject JUEL expressions into task queries (stored filters or ad-hoc queries) that the engine evaluated, allowing remote code execution and privilege escalation. Task filter expressions are now restricted to a whitelist, introduced as opt-in in 2.2.2 and now enabled by default. Affects the process engine. (since 2.2.4)

  • CVE-2026-114943 - Vulnerability in the Java runtime that an unauthenticated attacker with network access can exploit, though with difficulty. Affects openjdk21-jre-headless. - CVSS 6.5. (since 2.2.5)

  • CVE-2026-114944 - Vulnerability in the Java runtime that an unauthenticated attacker with network access can exploit, though with difficulty. Affects openjdk21-jre-headless. - CVSS 5.9. (since 2.2.5)

  • CVE-2026-114945 - Vulnerability in the Java runtime that an unauthenticated attacker with network access can exploit. Affects openjdk21-jre-headless. - CVSS 5.3. (since 2.2.5)

  • CVE-2026-114946 - Vulnerability in the Java runtime that an unauthenticated attacker with network access can exploit, though with difficulty. Affects openjdk21-jre-headless. - CVSS 4.8. (since 2.2.5)

  • CVE-2026-4738 - Out-of-bounds memory access in the infback9 module of zlib. Affects zlib. (since 2.2.5)

  • CVE-2026-55956 - Apache Tomcat ignores the methods and method omissions of security constraints defined for the default servlet. Affects org.apache.tomcat.embed:tomcat-embed-core, org.apache.tomcat:tomcat-catalina. - CVSS 6.5.

Low Severity
  • CVE-2026-107928 - When curl is built with GnuTLS, a malicious WebSocket server can make curl send memory past its send buffer. Affects libcurl, curl. - CVSS 4.8. (since 2.2.5)
  • CVE-2026-107929 - A CURLOPT_INTERFACE binding with the if!, host! or ifhost! prefix is not part of libcurl’s connection reuse key, so a later transfer that asks for a different source can silently reuse a connection bound to another interface. Affects libcurl, curl. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-83376 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via TLS to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-86409 - Setting CURLOPT_AWS_SIGV4 to NULL but does not disable SigV4 authentication, contrary to expectations and documentation. Affects libcurl, curl. - CVSS 5.3. (since 2.2.5)
  • CVE-2026-86410 - A flaw in the curl command line tool’s logic makes it only set SSH host verification options when interacting directly using SFTP or SCP, and not as a result of following a redirect. Affects libcurl, curl. - CVSS 6.8. (since 2.2.5)
  • CVE-2026-86411 - An ftp:// transfer configured with CURLUSESSL_NONE can reuse a pooled FTP control connection that a previous easy handle upgraded with STARTTLS and authenticated using a client certificate. Affects libcurl, curl. - CVSS 5.9. (since 2.2.5)
  • CVE-2026-86412 - A remote HTTP server can set a cookie that curl accepts and writes to a Netscape cookie jar but cannot reload. Affects libcurl, curl. - CVSS 5.3. (since 2.2.5)
  • CVE-2026-86413 - When using an ambient user in a first transfer doing Negotiate authentication and asked to follow redirects, curl could pass on its credential details to an unrelated second origin when asked to redirect there. Affects libcurl, curl. - CVSS 5.3. (since 2.2.5)
  • CVE-2026-86414 - An HTTP proxy can trick libcurl into sending the origin’s credentials (Basic password, or a Negotiate/Kerberos ticket) to the proxy itself, by answering the CONNECT tunnel request with 401 WWW-Authenticate: instead of the expected 407 Proxy-Authenticate:. Affects libcurl, curl. - CVSS 6.5. (since 2.2.5)
  • CVE-2026-86415 - libcurl’s connection cache ignores the automatic client certificate option, so an already authenticated Schannel connection can be reused for a transfer redirected to a different origin. Affects libcurl, curl. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-87255 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE. Affects openjdk21-jre-headless. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-87292 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-87367 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-87861 - When using ambient user credentials, an HTTP request directed to one origin may be dispatched over a connection previously authenticated via Negotiate for a different origin, leaving the request’s intended credentials unused. Affects libcurl, curl. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-87862 - Importing a includeSubDomains parent HSTS entry before a longer-lived child entry, silently drops the child. Affects libcurl, curl. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-87863 - An authenticated HTTPS origin can supply an HSTS max-age value that the parser accepts, but time serialization later fails to process. Affects libcurl, curl. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-87864 - The server reads only $N$ bytes for the payload, causing the remaining overflow bytes to be interpreted and executed as pipelined IMAP commands within the authenticated session. Affects libcurl, curl. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-87865 - When libcurl uses libssh2 with a hashed known_hosts file, an unrelated initial entry can cause host key validation to report a key mismatch as a missing key to the CURLOPT_SSH_KEYFUNCTION callback. Affects libcurl, curl. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-87866 - When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer does not possess. Affects libcurl, curl. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-91335 - Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 2.6. (since 2.2.5)
  • CVE-2026-91381 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-91397 - Difficult to exploit vulnerability allows an unauthenticated attacker with logon to the infrastructure to compromise Oracle Java SE, Oracle GraalVM for JDK and Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 3.6. (since 2.2.5)
  • CVE-2026-91400 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 3.1. (since 2.2.5)
  • CVE-2026-91402 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle JavaFX, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 3.1. (since 2.2.5)
  • CVE-2026-91461 - Difficult to exploit vulnerability allows unauthenticated attacker with network access via TLS to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-92386 - When writing a long cookie name and value to a Netscape cookie jar, a remote HTTP server can make curl write a record that exceeds its line-length parsing limit. Affects libcurl, curl. - CVSS 4.3. (since 2.2.5)
  • CVE-2026-92387 - By permanently omitting the final control-response line, a malicious FTP, IMAP, POP3, or SMTP server can exploit libcurl and completely bypass its configured transfer timeout mechanism, indefinitely blocking all concurrent transfers bound to the same multi-handle. Affects libcurl, curl. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-92389 - libcurl’s TFTP state machine fails to validate state transitions against the requested transfer direction, accepting opening server responses for both reads and writes interchangeably. Affects libcurl, curl. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-92390 - This flaw allows an HTTP(S) server to overwrite an existing local file specified in the Content-Disposition header despite the presence of the -J non-overwrite constraint. Affects libcurl, curl. - CVSS 6.5. (since 2.2.5)
  • CVE-2026-92391 - A deeply nested multipart MIME structure constructed via the public API causes a stack overflow in libcurl during normal cleanup operations. Affects libcurl, curl. - CVSS 3.7. (since 2.2.5)
  • CVE-2026-94265 - When processing an HTTP redirect to a URL containing userinfo (a username:password component), curl might erroneously retain and re-transmit the original host’s HTTP Negotiate authentication state. Affects libcurl, curl. - CVSS 3.1. (since 2.2.5)
  • CVE-2026-94266 - libcurl could accidentally return a URL for curl_easy_getinfo()’s CURLINFO_EFFECTIVE_URL option containing credentials, even though neither the URL provided to libcurl nor the redirected URL did. Affects libcurl, curl. - CVSS 3.3. (since 2.2.5)
  • CVE-2026-34180 - Heap buffer over-read in openssl ASN.1 decoder when parsing a crafted DER-encoded structure with a primitive element exceeding 2 GB, potentially causing a crash on 64-bit Unix platforms. Fixed in openssl 3.5.7-r0 (Alpine base image). (since 2.2.1)
  • CVE-2026-34181 - Insufficient PBMAC1 integrity validation in openssl PKCS#12 processing, giving an attacker a 1-in-256 chance of having a forged certificate and private key accepted. Fixed in openssl 3.5.7-r0 (Alpine base image). (since 2.2.1)
  • CVE-2026-42766 - NULL pointer dereference in openssl CMS password-based decryption when the optional keyDerivationAlgorithm field is absent, causing Denial of Service. Fixed in openssl 3.5.7-r0 (Alpine base image). (since 2.2.1)
  • CVE-2026-42767 - NULL pointer dereference in openssl CMP client when processing a crafted server response with a missing algorithm parameters field in an EncryptedValue, causing Denial of Service. Fixed in openssl 3.5.7-r0 (Alpine base image). (since 2.2.1)
  • CVE-2026-42768 - CMS_decrypt() and PKCS7_decrypt() in openssl vulnerable to a Bleichenbacher-style adaptive chosen-ciphertext attack when the attacker can supply CMS messages and observe error codes or decryption output. Fixed in openssl 3.5.7-r0 (Alpine base image). (since 2.2.1)
  • CVE-2026-42769 - CMP root CA key update verification rendered ineffectual in openssl due to a certificate chain building typo, potentially allowing a Registration Authority to substitute an arbitrary root CA. Fixed in openssl 3.5.7-r0 (Alpine base image). (since 2.2.1)
  • CVE-2026-42770 - DHX (X9.42) subgroup membership check in openssl uses the peer’s q parameter instead of the local key’s, enabling small-subgroup private key recovery (Lim-Lee attack). Fixed in openssl 3.5.7-r0 (Alpine base image). (since 2.2.1)
  • CVE-2026-45446 - AES-SIV and AES-GCM-SIV in openssl fail to recompute the expected authentication tag when decrypting with an empty ciphertext, allowing universal message forgery via the all-zeros tag. Fixed in openssl 3.5.7-r0 (Alpine base image). (since 2.2.1)
  • CVE-2026-7383 - Signed integer overflow in openssl ASN1_mbstring_ncopy() when computing the Unicode output buffer size for large inputs, potentially leading to heap buffer overflow. Fixed in openssl 3.5.7-r0 (Alpine base image). (since 2.2.1)
  • CVE-2026-9076 - Heap out-of-bounds read in openssl CMS PWRI key unwrap when an attacker-chosen stream-mode KEK cipher bypasses the block-size guard in kek_unwrap_key(), potentially causing Denial of Service. Fixed in openssl 3.5.7-r0 (Alpine base image). (since 2.2.1)
  • CVE-2026-47010 - Difficult to exploit vulnerability allows an unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 3.7. (since 2.2.2)
  • CVE-2026-47059 - Difficult to exploit vulnerability allows an unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition. Affects openjdk21-jre-headless. - CVSS 3.7. (since 2.2.2)
  • CVE-2026-13608 - [Unknown description]. Affects curl, libcurl. (since 2.2.3)
  • CVE-2026-14457 - Impact summary: The impact is limited to a possible Denial of Service as a result of an application abort, no data disclosure or remote command execution are possible. Affects libcrypto3, libssl3. - CVSS 7.5. (since 2.2.3)
  • CVE-2026-18924 - Description Not Available. Affects curl, libcurl. (since 2.2.3)
  • CVE-2026-19931 - A flaw in libcurl makes it wrongly reuse an HTTP connection setup for a given hostname using Negotiate authentication, when the initial request is done using empty credentials. Affects curl, libcurl. (since 2.2.3)
  • CVE-2026-54874 - Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service. Affects libcrypto3, libssl3. - CVSS 7.5. (since 2.2.3)
  • CVE-2026-63073 - Percent characters survive the conversion, so a sender DN such as “CN=%s%n” reaches BIO_vsnprintf() as an attacker-controlled format string with no matching variadic arguments. Affects libcrypto3, libssl3. - CVSS 5.9. (since 2.2.3)
  • CVE-2026-63074 - This exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends messages intending to be rejected with a large list of additional certificates repeatedly, forcing the server to store them indefinitely. Affects libcrypto3, libssl3. - CVSS 7.5. (since 2.2.3)
  • CVE-2026-63075 - Impact summary: A remote peer that can complete a QUIC handshake can cause connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially with sustained traffic or many concurrent QUIC connections. Affects libcrypto3, libssl3. - CVSS 7.5. (since 2.2.3)
  • CVE-2026-75803 - Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success without verifying the supplied authentication tag when the operation is finalized by calling the EVP_Cipher() function. Affects libcrypto3, libssl3. (since 2.2.3)
  • CVE-2026-80229 - [Unknown description]. Affects curl, libcurl. (since 2.2.3)
  • CVE-2026-80230 - Bypassing the pinning check under these disabled-verification conditions allows unauthenticated connections to succeed when they should be rejected. Affects curl, libcurl. (since 2.2.3)
  • CVE-2026-80231 - Description Not Available. Affects curl, libcurl. (since 2.2.3)
  • CVE-2026-80255 - [Unknown description]. Affects curl, libcurl. (since 2.2.3)
  • CVE-2026-80256 - Vulnerability fixed by upgrading the affected package. Affects curl, libcurl. (since 2.2.3)
  • CVE-2026-82208 - [Unknown description]. Affects curl, libcurl. (since 2.2.3)
  • CVE-2026-82209 - Consequently, the cookie is inappropriately included in subsequent outbound requests or HTTP redirects to arbitrary sibling subdomains under the same public suffix (e.g., attacker.co.uk). Affects curl, libcurl. (since 2.2.3)
  • CVE-2026-106449 - LZ4BlockInputStream with stopOnEmptyBlock set to false recursively calls refill() for each empty block, so a long sequence of empty blocks in an attacker-controlled stream can exhaust the decoding thread’s stack. Affects at.yawk.lz4:lz4-java. - CVSS 3.7. (since 2.2.4)

Build & Configuration

  • All artifacts are built for Java 17 and against Jakarta EE 11
  • The Spring Boot 3 and Spring Boot 4 builds are merged: the unsuffixed artifacts are built on Spring Boot 4, and the -4 artifacts are relocations
  • The engine jar shades only Gson and cron-utils; cibseven-spin-dataformat-all relocates Jackson 3, JAXB and Activation
  • GraalJS 25 is packaged as separate runtime modules in Run, Tomcat and WildFly, with icu4j packaged explicitly
  • WildFly: new Jackson 3 modules, and a module alias keeps the 2.2 module name org.cibseven.spin.cibseven-spin-dataformat-xml-dom-jakarta resolvable
  • The cibseven-bom manages json-path, json-smart and cibseven-external-task-client-jackson2, and no longer lists cibseven-engine-spring-6, the -jakarta artifacts or the legacy web applications
  • New database indexes ACT_IDX_TASK_PARENT_TASK_ID (on all databases) and ACT_IDX_HI_JOB_LOG_DEPLOYMENT speed up completing or deleting process instances with tasks and deleting deployments in cascade; building the second index on a large job log takes time, and on PostgreSQL, Oracle and SQL Server it blocks writes to ACT_HI_JOB_LOG while it is built
  • The SQL scripts of the webclient tables ship as <db>_extensions_<version>.sql and <db>_extensions_2.2_to_3.0.sql, and Liquibase applies them with the changeSet 2.2-to-3.0-extensions
  • The webclient publishes configuration metadata for IDE completion of cibseven.webclient.*
  • The modeler bundle is loaded only when the modeler is opened
  • Webjar dependencies are optional (since 2.2.3)
  • JDBC drivers are no longer on the webclient’s runtime classpath (since 2.2.2)
  • SBOMs (CycloneDX) are published for the whole project, the distributions and the Docker images
  • The enterprise webclient builds against cibseven-engine-rest-core instead of cibseven-engine-rest-core-jakarta (EE exclusive)
  • The modeler and the chat use a persistence unit and transaction manager of their own, so an embedding application keeps its own entityManagerFactory and transactionManager (EE exclusive)
  • The EE Docker images in the release repository are no longer tagged with the moving latest tags; use the version tags (EE exclusive) (since 2.2.4 hotfix)

On this Page: