Confluence Updates & Release Notes

Follow

147 updates curated from 173 sources by the Releasebot Team. Last updated: Nov 4, 2026

Get this feed:
  • Nov 3, 2026
    • Date parsed from source:
      Nov 3, 2026
    • First seen by Releasebot:
      Nov 4, 2026
    Atlassian logo

    Confluence by Atlassian

    Issues resolved in 11.0.1

    Confluence releases version 11.0.1, a bug-fix update that improves Kubernetes token reloading, PDF exports, mail archives, notification handling, and trash cleanup.

    The Atlassian Confluence team is pleased to announce the release of Confluence 11.0.1, which is a bug-fix release.

    Don't have Confluence 11.0 yet?

    Check out the new features and other highlights in the Confluence 11.0 release notes.

    Get the latest version

    We recommend you read the Confluence 11.0 release notes and you back up your confluence-home directory and database before upgrading.

    Released on 03 November 2026

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution CONFSERVER-104494 Confluence DC does not reload rotated Kubernetes projected service-account tokens Bug Oct 09, 2026 14:08 Nov 03, 2026 08:37 Edward Tejaswini P Medium CLOSED Fixed CONFSERVER-95936 PDF space export changes the page title when special characters like <>& are present in the page title Bug Jun 06, 2024 08:26 Nov 03, 2026 08:37 Pille Saral Juwin Zam Medium CLOSED Fixed CONFSERVER-87537 OutOfMemoryError caused by non-delivered mails/notifications accumulated in the ErrorQueue Bug Jun 08, 2023 11:35 Nov 03, 2026 08:37 Abhiraj Saxena Iker Alonso Medium CLOSED Fixed CONFSERVER-104497 Opening an archived mail in a space's Mail Archive fails with HTTP 500 "System Error" when the space has a mail account configured Bug Oct 14, 2026 10:26 Nov 03, 2026 08:37 agawron Shruthi Hebbal Low CLOSED Fixed CONFSERVER-76019 Purge All trash with custom content will run forever and never finish. Bug Jan 13, 2022 06:41 Nov 03, 2026 08:37 Tom Smallridge Quan Pham Low CLOSED Fixed Original source
  • Nov 3, 2026
    • Date parsed from source:
      Nov 3, 2026
    • First seen by Releasebot:
      Nov 4, 2026
    Atlassian logo

    Confluence by Atlassian

    Issues resolved in 10.2.20

    Confluence releases version 10.2.20 with bug fixes for Kubernetes token reloading, accessibility, PDF exports, notification queues, archived mail errors, and trash cleanup, improving reliability for Confluence Data Center users.

    The Atlassian Confluence team is pleased to announce the release of Confluence 10.2.20, which is a bug-fix release.

    Don't have Confluence 10.2 yet?

    Check out the new features and other highlights in the Confluence 10.2 release notes.

    Get the latest version

    We recommend you read the Confluence 10.2 release notes and you back up your confluence-home directory and database before upgrading.

    Released on 03 November 2026

    • CONFSERVER-104494 — Confluence DC does not reload rotated Kubernetes projected service-account tokens
    • CONFSERVER-104492 — Keyboard focus indicators are missing for some controls on page view in Confluence 10.2.17+
    • CONFSERVER-95936 — PDF space export changes the page title when special characters like <>& are present in the page title
    • CONFSERVER-87537 — OutOfMemoryError caused by non-delivered mails/notifications accumulated in the ErrorQueue
    • CONFSERVER-104497 — Opening an archived mail in a space's Mail Archive fails with HTTP 500 "System Error" when the space has a mail account configured
    • CONFSERVER-76019 — Purge All trash with custom content will run forever and never finish.

    6 issues

    Original source
  • All of your release notes in one feed

    Join Releasebot and get updates from Atlassian and hundreds of other software products.

    Create account
  • Oct 8, 2026
    • Date parsed from source:
      Oct 8, 2026
    • First seen by Releasebot:
      Oct 24, 2026
    Atlassian logo

    Confluence by Atlassian

    Confluence 11.0 release notes

    Confluence releases version 11.0 with stronger default security protections, rate limiting, faster indexing, and experimental asynchronous macro execution. The major Data Center update also modernizes its platform and removes legacy features, so administrators and app developers should review upgrade requirements and compatibility changes.

    We're excited to present Confluence 11.0

    Highlights

    • Rate Limiter Settings Enabled By Default
    • Rate-limit REST endpoints with annotations
    • Confluence Mobile Web Deprecation
    • AUI 11
    • Asynchronous Macro Execution
    • Modernizing and Securing Plugin Data Storage
    • Enhanced Security with New Content Security Policy
    • Enhanced protection against SSRF
    • Custom HTML Editing Now Disabled by Default
    • Journal Index Queue Improvements
    • Standardize JNDI path validation
    • Platform Upgrades for Stability and Resilience
    • Logging Modernization to log4j2.xml
    • Synchrony logging configuration now uses Log4j 2
    • Look and Feel Layouts and Customization Editing Now Disabled by Default
    • Restore From Local Drive Now Disabled by Default
    • Removal of support for transformed apps
    • Sign SAML authentication requests
    • V3 Attachment Storage Removal

    Further Information

    • Supported platforms changes
    • End of support announcements
    • App developers
    • Upgrade steps
    • Resolved issues

    This Confluence release supports only Data Center licenses. If you have a Server license, check out your options for upgrading.

    More

    Read the full list of issues for important info about the resolved issues in this release.

    Rate Limiter Settings Enabled By Default

    For: ADMINS

    Confluence 11.0 enables rate limiting by default for automation and application requests. This helps protect Confluence from request bursts that can affect instance stability and availability.

    Existing configurations are preserved: If rate limiting is already enabled on your Confluence instance, upgrading to Confluence 11.0 does not change your existing rate-limiting mode or configured limits.

    After upgrading, review your rate-limiting configuration in the administration interface. The default limits are intended to suit typical instances, but you can adjust or disable them to match your traffic patterns and integration requirements.

    Important for administrators: If you use high-volume automation or integrations, validate their request rates after upgrading and tune the configured limits as needed.

    Rate-limit REST endpoints with annotations

    For: ADMINS

    We've added the ability to rate limit individual REST API endpoints, so a single script, automation, or integration can no longer degrade your instance by hammering one expensive endpoint. Limits apply per user, per node, and requests that exceed them receive an HTTP 429 response with a Retry-After header telling the user when to try again.

    As an administrator you can tune or switch off any of these limits using JVM system properties in the com.atlassian.ratelimiting.api.* namespace, without waiting for an app update. This complements the existing rate limiting in your admin settings, which caps a user's total traffic rather than their use of a specific endpoint.

    Confluence Mobile Web Deprecation

    For: ADMINS

    We have disabled the legacy Confluence mobile web interface in Confluence 11.0. This change does not affect the Confluence Data Center mobile app.

    When users access Confluence from a mobile browser, Confluence now prompts them to either:

    • download the Confluence Data Center mobile app, or
    • continue to the desktop version of Confluence in their browser.

    Existing links to the former mobile interface redirect to the corresponding standard Confluence page where possible.

    AUI 11

    For: ADMINS

    We’re introducing AUI 11 with the next major versions of our Data Center products, bringing a refreshed visual experience that aligns more closely with Atlassian Cloud. The update includes refreshed badges, banners, and application headers, a modernised icon set, and updated typography using Atlassian fonts and design system themes.

    If you use Marketplace apps or custom in-house apps with a frontend, ensure they’re compatible with the new major version before upgrading.

    Asynchronous Macro Execution

    For: ADMINS EXPERIMENTAL

    Confluence Data Center now supports asynchronous macro execution — a major performance capability that changes how macros are rendered on a page.

    Previously, every macro on a Confluence page was executed sequentially on the same HTTP request thread. The browser couldn't receive the page until every last macro had finished — meaning a single slow macro (e.g. a Jira query or a blog-posts roll-up) could block an entire page load for all users.

    With this release, macros can be configured to execute asynchronously and concurrently in a dedicated thread pool. The HTTP request thread is freed immediately, and macro results are assembled as they complete. For pages with multiple slow macros, this can dramatically reduce perceived load time.

    Configuration required: Yes (opt-in per macro, admin setup)

    Concurrent execution

    Multiple macros on the same page can now execute in parallel rather than sequentially, significantly reducing total page render time.

    Deduplication

    If multiple users request the same page simultaneously, identical macro executions (same macro, same parameters, same content) can be deduplicated — one execution runs and its result is shared, avoiding redundant parallel work.

    Configurable timeouts and rate limits

    Administrators can set per-macro time limits and concurrency limits via the REST API, with global defaults configurable via JVM system properties. If a macro exceeds its time limit, Confluence can signal it to stop gracefully.

    Result caching (opt-in)

    Macro results can be cached per-user on each node, so repeat visits to the same page don't re-execute expensive macros. Cache TTL and size are configurable.

    Execution cancellation

    Administrators can cancel in-flight macro executions in real time — by execution ID, by macro name, or all at once — via REST API. Macro developers can implement graceful cancellation support.

    Observability

    Active macro executions are visible in real time, both via REST API and (on clustered setups) in the Confluence Clustering UI. A scheduled analytics job publishes execution statistics for monitoring.

    Safe fallback

    If the async thread pool is saturated (queue full or queue latency exceeded), macros fall back to synchronous execution automatically. No requests are dropped.

    How to get started

    This feature is disabled by default and requires administrator configuration:

    1. Enable the dark feature atlassian.macros.async.execution in Confluence Dark Features
    2. Use the REST API (PUT /rest/asyncmacros/latest/execution-controls) to configure which macros run asynchronously
    3. Optionally tune thread pool and timeout settings via JVM system properties

    Modernizing and Securing Plugin Data Storage

    For: ADMINS

    Removal of legacy structures for storing plugin data will secure Confluence for long term stability. After making these legacy systems read-only in Confluence 10.0, we have removed them entirely in Confluence 11.0. This includes the Removal of Bandana, and the removal of OpenSymphony PropertySet (osProperty). For security reasons, Confluence 11.0 will also no longer bundle the XStream library.

    Direct access to the Bandana database table and OpenSymphony PropertySet will no longer be possible in Confluence 11.0. Please ensure all Apps that currently use Bandana are migrated to alternative storage (for example, Active Objects or SAL Plugin Settings) before upgrading to Confluence 11.

    To make this feasible, upgrade to Confluence 11.0 will be supported only from the latest Confluence 10.2.x release (that is, customers must upgrade to the latest 10.2.13+ before upgrading to 11.0).

    Migrating data will no longer be possible in Confluence 11.0 - you must complete migration before you upgrade.

    For migration guidance, refer to Preparing for Confluence 10.0 for more information.

    The BANDANA table is deprecated and will be removed automatically in a future release. You can drop it now by setting -Dconfluence.enable-drop-bandana-table=true before the upgrade. Back up the table before doing so if you want to retain the data.

    Enhanced Security with New Content Security Policy

    For: ADMINS

    In Confluence 11, the content security policy (CSP) for the "script-src" directive has been introduced. The following adjustments apply:

    1. All direct and indirect uses of eval are blocked.
    2. All inline scripts are blocked.
    3. Scripts loaded from other domains must be allowed via the CSP script-src header.
    4. Script tags with inline code must include a nonce attribute.
    5. Keyboard shortcuts with operation type execute are no longer supported.

    How is script-src CSP enabled

    Confluence 11 enables this by default alongside existing policies. Only system administrators can disable this feature via the configuring of system properties:

    http.header.security.content.security.policy.strictness.enabled

    (e.g. -Dhttp.header.security.content.security.policy.strictness.enabled=false)

    The CSP report-only mode is disabled when the property CSP is enabled (set to true).

    There is also a system property http.header.security.content.security.scriptsrc.additional.urls that let admins to allow external scripts if they are needed.

    Enhanced protection against SSRF

    For: ADMINS

    We’re introducing two security enhancements for Confluence, Jira Software, and Jira Service Management Data Center to strengthen protection against Server-Side Request Forgery (SSRF) attacks. These changes help block unauthorized outbound requests to sensitive destinations, ensuring your instance remains secure.

    Key changes include:

    • New default outbound denylist: We’ve added a built-in denylist that automatically blocks requests to dangerous destinations, such as cloud metadata services (AWS, Google Cloud, Azure), private networks, and insecure protocols (for example, file:// and shell://).
    • Extended allowlist enforcement: Several platform components that previously bypassed the allowlist, including OAuth2, Gadgets, Webhooks, and the Universal Plugin Manager (UPM), now strictly follow your allowlist configuration.
    • DNS resolution checking: The denylist now resolves domain names to their IP addresses to prevent bypass attempts via DNS rebinding.

    These protections are enabled by default. They provide immediate security against SSRF attacks without requiring extra configuration. While you can disable the denylist using the -Dssrf.denylist.enabled=false JVM system property, we don’t recommend this for production environments.

    While a denylist blocks known-dangerous destinations, we recommend configuring a comprehensive allowlist. An allowlist is the most effective defense against SSRF because it limits outbound requests only to the specific, trusted destinations your instance needs to function.

    Custom HTML Editing Now Disabled by Default

    For: ADMINS

    To improve security, editing custom HTML is now disabled by default. If you need to enable custom HTML, set the confluence.custom.html.config.enabled system property to true. Only system administrators can enable this feature. How to configure system properties

    Journal Index Queue Improvements

    For: ADMINS

    The content index queue is now processed fairly across content types instead of strictly in queue order. Entries are grouped by content type (pages and blogs, attachments, comments, user profiles, custom content, other). As a result, A bulk operation on one content type — a mass attachment upload, a space import — can no longer delay indexing of everything queued behind it. Queue depth per content type is shown on the Content indexing admin page.

    This change applies to the content index journal (main_index) only; other journals keep the linear path.

    To turn off the fair Index queue, disable the confluence.fair.journal.index.queue dark feature.

    Concurrent Processing

    Due to the grouping of entries we can now process the entries in batches concurrently, increasing performance. A number of worker threads are made from the CPUs available to the JVM (capped at 50) and the index queue gives each worker at least 100 entries each to process.

    To fall back to serial processing, disable the confluence.fair.journal.index.queue.parallel.processing dark feature — no restart is needed.

    Standardize JNDI path validation

    For: ADMINS

    We’re standardizing how our products validate and use Java Naming and Directory Interface (JNDI) paths. Inconsistent checks across different products can sometimes allow crafted inputs to trigger unintended code execution. By unifying these validation processes, we're reducing the risk that a misconfiguration or an overlooked pathway could become a security entry point.

    This change helps protect your data and ensures service reliability by aligning all products on a single, safe approach to JNDI lookups.

    Platform Upgrades for Stability and Resilience

    For: ADMINS

    We have been busy at work upgrading the Confluence 11 platform to set Confluence up for success in the long term. In most cases these changes are transparent. However, if you use Marketplace apps or custom in-house apps, ensure they are compatible with the new major version before upgrading. Some of the more notable changes can be seen below.

    Update to jQuery 4

    We’re upgrading to jQuery 4 to align on jQuery versions across all Data Center products. This means a significant jQuery version uplift for products containing older versions of jQuery.

    Java 25 is now the minimum supported version

    Starting from Confluence 11, Java 25 is the minimum supported version for both compile and runtime environments. At the same time, all components run on JDK 25.

    Upgrade to React 19

    We're upgrading to React 19 across all Data Center products to keep our frontend dependencies secure and compliant. This change ensures we can continue upgrading other critical frontend libraries in the future.

    Modernize your outgoing network connections (HttpClient 5)

    We're modernizing how our products make outgoing network connections by removing an older networking component that's no longer actively maintained: Apache HttpClient 4. This change reduces long-term security and reliability risks and ensures our technology remains supported and aligned with current standards.

    Jakarta 11 and Spring 7 upgrade

    We’re updating our Jakarta and Spring dependencies to continue meeting your demands for secure and compliant products. This change ensures we stay aligned with security policies and receive the latest updates.

    Upgrade to Jackson 3

    We’ve upgraded the Jackson library to ensure your instance and apps are secure, compliant, and compatible with the latest industry standards.

    For most customers, this change won't affect how you use your apps. However, if you use or develop extensions, take note of the following:

    • We've notified Marketplace partners of this change. They're responsible for updating their apps to ensure continued compatibility.
    • If you've developed custom, in-house apps or integrations, your development team must update the Jackson 2 libraries to version 3 in your codebase.

    Logging Modernization to log4j2.xml

    For: ADMINS

    From Confluence 11.0, Log4j 1 configuration and API have been removed for security and modernization. As a result of this, the log4j.properties format will no longer be used and is replaced by log4j2.xml. Below are the affected files:

    Up to 10.2.x

    • /confluence/WEB-INF/classes/log4j.properties
    • /confluence/WEB-INF/classes/log4j-diagnostic.properties

    From Confluence 11.0

    • /confluence/WEB-INF/classes/log4j2.xml
    • /confluence/WEB-INF/classes/log4j2-diagnostic.xml

    Any log4j.properties left in place after an upgrade is ignored, not merged. Confluence logs a warning at startup if it finds these log4j property files. If you customised logging, re-apply those changes to log4j2.xml when upgrading, then delete log4j.properties to silence the warning. Setting log levels at runtime through Logging and Profiling in the admin UI is unchanged.

    Synchrony logging configuration now uses Log4j 2

    For: ADMINS

    Synchrony 7.0.13 (bundled in Confluence 11.0) no longer supports Log4j 1 configuration files or the legacy log4j.configuration system property.

    • If you do not use a custom Synchrony logging configuration, no action is required. Synchrony uses its bundled Log4j 2 configuration by default.
    • If you currently use a custom synchrony-log4j.properties file, convert it to a Log4j 2 XML configuration file and configure it using log4j2.configurationFile.

    Confluence-managed Synchrony

    Create a Log4j 2 XML configuration file, then add the following to your synchrony-args.properties file:

    log4j2.configurationFile=file:///absolute/path/to/synchrony-log4j2.xml
    

    Standalone Synchrony

    Create a Log4j 2 XML configuration file, then add the following to OPTIONAL_OVERRIDES in your start-synchrony.sh or start-synchrony.bat script:

    OPTIONAL_OVERRIDES="-Dlog4j2.configurationFile=file:///absolute/path/to/synchrony-log4j2.xml"
    

    Log4j 1 .properties files are not automatically converted or merged with Log4j 2 configuration.

    Look and Feel Layouts and Customization Editing Now Disabled by Default

    For: ADMINS

    To improve security, configuring Look and Feel customization is now disabled by default. Admins can only view existing layout configurations. To enable look and feel customization, set the confluence.custom.look.and.feel.enabled system property to true. Only system administrators can enable this feature.

    • Look and Feel customization will be disabled by default at both Global and Space level. Setting the system property to true will enable customization at both the places.
    • In addition to this, for Space level stylesheet configuration ensure that “Custom Stylesheets for Spaces” is enabled in Security Configuration.

    How to configure system properties

    Restore From Local Drive Now Disabled by Default

    For: ADMINS

    To improve application security, restoring of data from local drives is now disabled by default. To enable restoring of data from local drive , set confluence.restore.from.local.drive.enabled system property to true. Only system administrators can enable this feature via the configuring of system properties.

    Removal of support for transformed apps

    For: ADMINS

    We’re removing support for the transformed app format to improve the performance and reliability of Data Center products. Starting with this release, the Universal Plugin Manager (UPM) will no longer install or enable apps using this older format, and we’ve removed the infrastructure that converted these formats at startup. This change helps your instance start faster and reduces the risk of stability issues.

    Before you upgrade, ensure your Marketplace apps are compatible with <product name+version>. If you use custom in-house apps, you must migrate them to the transformerless format. The following guides might help you in this process:

    • How to automate the migration process
    • More about identifying and converting plugins

    Sign SAML authentication requests

    For: ADMINS

    We’re implementing signed Security Assertion Markup Language (SAML) authentication requests to strengthen your instance’s security. When SAML is enabled, the authentication plugin generates a certificate and private key during startup. The private key signs SAML authentication requests, and you can download the certificate to upload to your Identity Provider (IdP). This lets the IdP verify the authenticity and integrity of each request.

    To enable signing SAML authentication requests, go to the Authentication methods page and select Sign requests. Explore SAML single sign-on for Atlassian Data Center applications

    V3 Attachment Storage Removal

    For: ADMINS

    Confluence 8.1 introduced the v4 attachment layout and a background migration that moved attachment data from ver003 to v4. Confluence 11.0 removes version 3 (ver003) attachment storage entirely: the storage implementation, the automatic V3 → V4 migration, and the related APIs.

    Note that the V3 → V4 migration no longer runs in Confluence 11.0 and must have been completed prior to upgrading

    Supported platforms changes

    This section contains a run-down of all the changes that have been made to supported platforms since the last Confluence LTS release. See the complete list of supported platforms

    We’ve confirmed support for:

    • JDK 25
    • MySQL 8.4
    • Oracle AI Database 26ai (rebranded from Oracle 23ai)
    • PostgreSQL 17
    • OpenSearch 2.11 through to 12.19

    This version of Confluence runs only on Java 25.

    End of support announcements

    We've removed support for:

    • PostgreSQL 16
    • Aurora PostgreSQL 16
    • MS SQL Server 2019
    • Oracle 19c
    • Java 21

    We’ve deprecated support for:

    • MySQL 8.4
    • MS SQL Server 2022

    For more information on these notices, see End of Support Announcements for Confluence.

    App developers

    Head to Preparing for Confluence 11.0 to find out more about changes under the hood. These include but are not limited to:

    • Jsoup Upgrade
    • Frontend AMD and WRM Resources Removal
    • JQuery plugins removal
    • Removing Bundled Joda time
    • Atlassian Keyboard Shortcuts Upgrade

    Upgrade steps

    Always test the upgrade in a test environment before upgrading in production.

    To upgrade Confluence to the latest version:

    1. From the Administration menu, select Manage apps, and then Confluence update check to verify the compatibility of your user-installed apps with the target application version.
    2. From the Administration menu, select General Configuration, and then Plan your upgrade and the version you want to upgrade to. This will run the pre-upgrade checks.
    3. From the Administration menu, select General Configuration, and then Troubleshooting and support tools to check your license validity, application server, database setup, and more.
    4. If your version of Confluence is more than one version behind, read the release notes and upgrade guides for all releases between your version and the latest version.
    5. Back up your installation directory, home directory, and database.
    6. Download the latest version of Confluence.
    7. Follow the instructions in the Upgrade Guide.

    Update configuration files after upgrading

    The contents of configuration files such as server.xml, web.xml, setenv.bat/setenv.sh, and confluence-init.properties change from time to time.

    When upgrading, we recommend manually reapplying any additions to these files (such as proxy configuration, datasource, JVM parameters) rather than simply overwriting the file with the file from your previous installation; otherwise you will miss out on any improvements we have made.

    Upgrade instructions

    You must first upgrade to the latest Confluence 10.2 release first before upgrading to Confluence 11.0.

    Follow the usual upgrade instructions to upgrade your site.

    Been a while since your last upgrade? Check out our upgrade matrix for a bird's-eye view of the most important changes since Confluence 10.2 LTS.

    Don't forget to renew your software maintenance. Renew now

    Resolved issues

    For full details of bugs fixed and suggestions resolved, head to our public issues tracker on Jira.

    Issues resolved in 11.0.0

    Released on 08 October 2026

    Credits

    Our wonderful customers...

    You play an important role in making Confluence better. Thanks to everyone who participated in interviews with us, made suggestions, voted, and reported bugs!

    Original source
  • Oct 5, 2026
    • Date parsed from source:
      Oct 5, 2026
    • First seen by Releasebot:
      Oct 24, 2026
    Atlassian logo

    Confluence by Atlassian

    Issues resolved in 10.2.19

    Confluence releases version 10.2.19, a bug-fix update addressing security vulnerabilities across dependencies and a responsiveness issue in Confluence Data Center.

    The Atlassian Confluence team is pleased to announce the release of Confluence 10.2.19, which is a bug-fix release.

    Don't have Confluence 10.2 yet?

    Check out the new features and other highlights in the Confluence 10.2 release notes.

    Get the latest version

    We recommend you read the Confluence 10.2 release notes and you back up your confluence-home directory and database before upgrading.

    • CONFSERVER-104520 — BASM (Broken Authentication & Session Management) io.netty:netty-handler Dependency in Confluence Data Center
    • CONFSERVER-104516 — Improper Authorization org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center
    • CONFSERVER-104510 — BASM (Broken Authentication & Session Management) org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center
    • CONFSERVER-104509 — MITM (Man-in-the-Middle) org.apache.tomcat:tomcat-coyote Dependency in Confluence Data Center
    • CONFSERVER-104507 — Improper Authorization org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center
    • CONFSERVER-104488 — Arbitrary File Access in Confluence Data Center
    • CONFSERVER-104459 — Confluence 10.2 can become unresponsive when requests wait on a stalled cache load
    • CONFSERVER-104519 — Path Traversal (Arbitrary Read/Write) postcss Dependency in Confluence Data Center
    • CONFSERVER-104518 — DoS (Denial of Service) org.apache.tomcat:tomcat-coyote Dependency in Confluence Data Center
    • CONFSERVER-104517 — BASM (Broken Authentication & Session Management) org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center
    • CONFSERVER-104515 — DoS (Denial of Service) com.fasterxml.jackson.dataformat:jackson-dataformat-cbor, tools.jackson.dataformat:jackson-dataformat-cbor Dependency in Confluence Data Center
    • CONFSERVER-104512 — Improper Authorization org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center
    • CONFSERVER-104511 — DoS (Denial of Service) org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center
    • CONFSERVER-104508 — PrivEsc (Priviledge Escalation) org.apache.tomcat:tomcat-coyote Dependency in Confluence Data Center
    • CONFSERVER-104506 — MITM (Man-in-the-Middle) io.netty:netty-handler Dependency in Confluence Data Center
    • CONFSERVER-104504 — DoS (Denial of Service) org.springframework:spring-expression Dependency in Confluence Data Center
    • CONFSERVER-104503 — XSS (Cross Site Scripting) org.springframework:spring-web Dependency in Confluence Data Center
    • CONFSERVER-104502 — DoS (Denial of Service) org.springframework:spring-webmvc Dependency in Confluence Data Center
    • CONFSERVER-104501 — SSRF (Server-Side Request Forgery) fast-uri Dependency in Confluence Data Center
    • CONFSERVER-104514 — DoS (Denial of Service) nanoid Dependency in Confluence Data Center

    Showing 20 out of 27 issues

    Original source
  • Sep 8, 2026
    • Date parsed from source:
      Sep 8, 2026
    • First seen by Releasebot:
      Oct 24, 2026
    Atlassian logo

    Confluence by Atlassian

    Issues resolved in 10.2.18

    Confluence releases version 10.2.18, a bug-fix update that resolves issues with the Search V2 public API and app status updates in multi-node clusters.

    The Atlassian Confluence team is pleased to announce the release of Confluence 10.2.18, which is a bug-fix release.

    Don't have Confluence 10.2 yet?

    Check out the new features and other highlights in the Confluence 10.2 release notes.

    Get the latest version

    We recommend you read the Confluence 10.2 release notes and you back up your confluence-home directory and database before upgrading.

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution CONFSERVER-104457 Search V2 public API uses unexported package com.atlassian.confluence.search.v2.aggregator, breaking third-party apps Bug Sept 07, 2026 06:50 Oct 06, 2026 22:52 Manonmani Muthukrishnan Ganesh Gautam High CLOSED Fixed CONFSERVER-104456 Updating apps in a multi-node cluster can randomly revert an app/module status in PLUGIN_SETTING to their default status across the cluster Bug Sept 07, 2026 03:08 Sept 30, 2026 01:26 agawron Eric L High CLOSED Fixed Original source
  • Similar to Confluence with recent updates:

  • Sep 6, 2026
    • Date parsed from source:
      Sep 6, 2026
    • First seen by Releasebot:
      Oct 24, 2026
    Atlassian logo

    Confluence by Atlassian

    Issues resolved in 10.2.17

    Confluence releases version 10.2.17, a bug-fix update that addresses numerous security vulnerabilities and fixes an editor issue caused by an expired bundled TinyMCE license key.

    The Atlassian Confluence team is pleased to announce the release of Confluence 10.2.17, which is a bug-fix release.

    Don't have Confluence 10.2 yet?

    Check out the new features and other highlights in the Confluence 10.2 release notes.

    Get the latest version

    We recommend you read the Confluence 10.2 release notes and you back up your confluence-home directory and database before upgrading.

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution CONFSERVER-104505 Cryptographic Failure org.bouncycastle:bcprov-lts8on Dependency in Confluence Data Center Public Security Vulnerability Oct 16, 2026 01:45 Oct 20, 2026 17:01 Unassigned David Detweiler Highest PUBLISHED Fixed CONFSERVER-104454 Confluence editor broken — bundled TinyMCE license key (T8LK) expired on 2026-08-06 Bug Sept 06, 2026 06:59 Oct 16, 2026 05:48 Jiri Hronik Arun Suryawanshi Highest CLOSED Fixed CONFSERVER-104443 Injection Bouncy Castle Dependency in Confluence Data Center Public Security Vulnerability Sept 02, 2026 11:31 Sept 15, 2026 17:01 Unassigned Security Metrics Bot Highest PUBLISHED Fixed CONFSERVER-104434 BASM (Broken Authentication & Session Management) Bouncy Castle Dependency in Confluence Data Center Public Security Vulnerability Sept 02, 2026 11:30 Sept 15, 2026 17:01 Unassigned Security Metrics Bot Highest PUBLISHED Fixed CONFSERVER-104433 MITM (Man-in-the-Middle) Netty Dependency in Confluence Data Center Public Security Vulnerability Sept 02, 2026 10:31 Sept 15, 2026 17:01 Unassigned Security Metrics Bot Highest PUBLISHED Fixed CONFSERVER-104430 MITM (Man-in-the-Middle) Netty Dependency in Confluence Data Center Public Security Vulnerability Sept 02, 2026 08:31 Sept 15, 2026 17:01 Unassigned Security Metrics Bot Highest PUBLISHED Fixed CONFSERVER-104362 RCE (Remote Code Execution) at lodash dependency in Confluence Data Center Public Security Vulnerability Jul 11, 2026 04:31 Sept 15, 2026 17:01 Unassigned Security Metrics Bot Highest PUBLISHED Fixed CONFSERVER-104483 DoS (Denial of Service) io.netty:netty-codec-dns Dependency in Confluence Data Center Public Security Vulnerability Sept 25, 2026 01:33 Oct 20, 2026 17:01 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104476 Cryptographic Failure in org.bouncycastle:bcmail-lts8on Dependency in Confluence Data Center Public Security Vulnerability Sept 22, 2026 21:30 Oct 20, 2026 17:01 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104474 Injection ch.qos.logback:logback-core Dependency in Confluence Data Center Public Security Vulnerability Sept 20, 2026 15:34 Oct 20, 2026 17:01 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104473 DoS (Denial of Service) org.bouncycastle:bcutil-lts8on Dependency in Confluence Data Center Public Security Vulnerability Sept 20, 2026 15:33 Oct 20, 2026 17:01 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104472 Cryptographic Failure org.bouncycastle:bcprov-lts8on Dependency in Confluence Data Center Public Security Vulnerability Sept 20, 2026 15:33 Oct 20, 2026 17:01 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104471 RCE (Remote Code Execution) org.bouncycastle:bcprov-lts8on Dependency in Confluence Data Center Public Security Vulnerability Sept 20, 2026 15:32 Oct 20, 2026 17:01 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104470 Cryptographic Failure org.bouncycastle:bcprov-lts8on Dependency in Confluence Data Center Public Security Vulnerability Sept 20, 2026 15:32 Oct 20, 2026 17:01 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104469 Security Misconfiguration org.bouncycastle:bcprov-lts8on Dependency in Confluence Data Center Public Security Vulnerability Sept 20, 2026 15:31 Oct 20, 2026 17:01 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104451 DoS (Denial of Service) in Confluence Data Center Public Security Vulnerability Sept 04, 2026 04:31 Sept 15, 2026 17:00 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104445 DoS (Denial of Service) immutable.js Dependency in Confluence Data Center Public Security Vulnerability Sept 02, 2026 11:32 Sept 15, 2026 17:01 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104444 DoS (Denial of Service) immutable Dependency in Confluence Data Center Public Security Vulnerability Sept 02, 2026 11:32 Sept 15, 2026 17:01 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104442 DoS (Denial of Service) Bouncy Castle Dependency in Confluence Data Center Public Security Vulnerability Sept 02, 2026 11:31 Sept 15, 2026 17:01 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104441 BASM (Broken Authentication & Session Management) Bouncy Castle Dependency in Confluence Data Center Public Security Vulnerability Sept 02, 2026 11:31 Sept 15, 2026 17:01 Unassigned Security Metrics Bot High PUBLISHED Fixed

    Showing 20 out of 42 issues

    Original source
  • Sep 1, 2026
    • Date parsed from source:
      Sep 1, 2026
    • First seen by Releasebot:
      Oct 24, 2026
    Atlassian logo

    Confluence by Atlassian

    Issues resolved in 10.2.16

    Confluence releases version 10.2.16, a bug-fix update that resolves issues affecting page tasks, indexing, performance, startup logging, calendars, and attachment uploads.

    The Atlassian Confluence team is pleased to announce the release of Confluence 10.2.16, which is a bug-fix release.

    Don't have Confluence 10.2 yet?

    Check out the new features and other highlights in the Confluence 10.2 release notes.

    Get the latest version

    We recommend you read the Confluence 10.2 release notes and you back up your confluence-home directory and database before upgrading.

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution CONFSERVER-103693 Child page tasks not visible on user profile when parent page has 'Can view and edit' restrictions Bug May 01, 2026 13:06 Oct 09, 2026 07:10 Jeffery Xie Bibek Roy Highest CLOSED Fixed CONFSERVER-104410 Confluence 9.2.23 Linux .bin installer silently ignores sys.installationDir in unattended (-q) mode Bug Aug 20, 2026 19:48 Sept 09, 2026 13:57 Akshay Rai Eleno Diaz High CLOSED Fixed CONFSERVER-104325 Incremental index flush path does not skip AntiSamy re-clean, causing OutOfMemoryError on large pages/complex storage format Bug Jul 03, 2026 23:03 Sept 01, 2026 05:33 Aug 29, 2026 Ayush Deothia Arun Suryawanshi High CLOSED Fixed CONFSERVER-104380 SLF4J "No SLF4J providers were found" warning appears during Confluence data center startup Bug Jul 23, 2026 06:09 Sept 09, 2026 13:57 Tom Smallridge Tejaswini P Medium CLOSED Fixed CONFSERVER-104343 Slowness during space/page creation due to excessive permission checks in Confluence Datacenter Bug Jul 10, 2026 11:33 Oct 09, 2026 07:10 Quan Pham Tejaswini P Medium CLOSED Fixed CONFSERVER-104389 The AccessLogValve configuration in Confluence 10 and beyond contains the wrong time unit designation Bug Aug 05, 2026 06:31 Sept 01, 2026 05:33 Niraj Bhawnani Malcolm Ninnes Low CLOSED Fixed CONFSERVER-104366 High number of DB calls to fetch application links on every page load, and many network requests on page load when portfolio insight connection is configured Bug Jul 16, 2026 23:27 Sept 09, 2026 13:57 Benjamin Suess Benjamin Suess Low CLOSED Fixed CONFSERVER-104101 Reminder Emails for Teams Calendar are not triggered Bug May 29, 2026 08:24 Oct 09, 2026 07:10 Saquia Naz Disha Rathore Low CLOSED Fixed CONFSERVER-101052 Uploading an attachment from 'Insert link' dialog displays an error message despite success Bug Sept 24, 2025 00:50 Oct 09, 2026 07:10 Jeffery Xie Kusal Kithul-Godage Low CLOSED Fixed Original source
  • Aug 17, 2026
    • Date parsed from source:
      Aug 17, 2026
    • First seen by Releasebot:
      Aug 17, 2026
    Atlassian logo

    Confluence by Atlassian

    Your next presentation is already in Confluence

    Confluence adds Slides, a faster way to turn existing team knowledge into presentation-ready decks with Rovo. It creates context-rich slides from prompts and connected content, generates visuals, supports inline editing and collaboration, and lets teams present without leaving Confluence.

    The pain of building decks the old way

    You know the drill when it comes to creating presentations. The afternoons spent creating a deck from scratch – aligning text boxes, copy and pasting images, moving the slides around to find the right flow, the list goes on and on. The problem isn’t that the story isn’t there. It’s that getting the story out onto slides takes way more time than it should.

    That’s where Confluence slides comes in. It’s the fastest way to transform existing knowledge into a presentation-ready deck in seconds — no blank slide, no copy-paste, no app-switching. Simply describe what you want and watch Rovo generate context-rich presentations in real-time.

    Creating a deck shouldn’t be hard. But for most teams, it is. The manual effort of building decks the old way is painful, and the numbers are hard to ignore:

    • 37% of total time spent in PowerPoint goes to formatting — adjusting colors, fonts, and layouts instead of refining the actual message (Source: Nielsen)
    • 42% of that time is wasted searching for the right templates, icons, or past slides (Source: Nielsen)
    • Corporate professionals spend roughly 7 hours per week on slide tasks, costing an estimated $25,500 per year per employee in lost productivity (Source: Nielsen)

    Teams don’t lack ideas or content. They lack a better, faster way to turn what they already know into a story they can easily share. The result is that every deck starts from scratch, even when the content already exists somewhere.

    Say hello to Confluence Slides

    With Confluence slides, teams now have a new way of creating slides with Rovo, slides that are context-rich and generated with AI in seconds. Rovo pulls context from across Atlassian and connected third-party apps like Slack and Google Drive to create impactful, visual presentations grounded in your team’s work. Simply ask Rovo to create or edit your slides and it’ll determine slides structure, create content, and even build visualizations like charts and graphs — all from a single prompt. You’ll be able to collaborate and present your slides directly in Confluence, without breaking the flow of work and having to switch apps.

    A few ways teams can use Confluence slides:

    • Project kickoffs — Generate a presentation-ready kickoff deck from your project brief, complete with visuals like a timeline chart to get stakeholders bought in from day one.
    • Campaign analysis readouts — Turn campaign performance data and retrospective notes into a visual deck, with bar charts and funnel charts generated from data already in Atlassian.
    • Customer pitches — Spin up a tailored customer pitch deck from existing account notes, case studies, and competitive intel in Confluence.

    A closer look at Confluence slides

    Your team’s knowledge already lives in Confluence — now it can be turned into a polished deck in seconds with Confluence slides. Start with a prompt, refine with Rovo, and present your new visual presentation with confidence, all without leaving Confluence.

    Create from context, not from scratch

    Today, your team’s knowledge is scattered across docs, projects, and meeting notes, so every deck starts from a blank slide. Figuring out what to include and how to structure the story takes as long as making the deck itself. Confluence slides fixes that.

    • Powered by the Teamwork Graph: Rovo pulls context from across Atlassian and connected third-party sources like Slack, Google Docs, Microsoft Excel so your deck is grounded in real team knowledge.
    • Narrative structure built for you: Rovo determines what to include, how to sequence it, and how to frame the story.
    • No blank slate: Creation always starts from existing content or a simple prompt, so you’re never stuck staring at a blank slide.

    From first draft to final story — fast

    Getting from a first draft to something presentation-ready takes longer than it should — every small change means more manual work. Confluence slides keeps the momentum going, with Rovo doing the heavy lifting for you.

    • Impactful visuals to tell your story: Automatically generates charts, timelines, bar graphs, and images directly within a slide — so your deck is polished and presentation-ready from the first draft.
    • Rovo-powered editing: Use Rovo to make edits inline, such as restructuring, rewriting, or improving your slides.
    • Quick manual edits: Put the finishing touches directly on the slide yourself, such as editing text or reorganizing slides from the filmstrip.

    Collaborate and present, all in Confluence

    When your deck lives in a different tool from your knowledge, things drift. Teams end up maintaining two separate artifacts — the doc in Confluence, the deck somewhere else — and it’s rarely clear which is current. With Confluence slides, that split disappears. Your slides live where your knowledge lives, so you can create, share, collaborate, and present your work in one place.

    • Real-time collaboration: Invite teammates to collaborate on a deck, with inline comments to gather feedback and align stakeholders.
    • Present directly from Confluence: Hit presentation mode and go — no exporting, no app-switching, no friction between finishing and presenting.
    • Respects Confluence permissions: Slides live in the Confluence content tree, inheriting existing space and page permissions so access is always controlled.

    Tips to get the most out of Confluence slides

    Can’t wait to get started? Getting to a great deck is faster when you give Rovo the right starting point. Here are a few tips:

    1. Provide your sources upfront
      Link to the exact pages, Jira projects, or 3rd party connector you want used. You can also have Rovo follow a specific slide template by linking to it.
      “Create slides based on [this project poster] and [this Q3 retro]. Use the data from the retro as the primary source. Use this deck as the template — match its slide layouts: [link].”

    2. Set your brand colors
      Hex codes work best, but Rovo can also interpret color descriptions, vibes, or links to a company website.
      “Use our brand colors: 0052CC and FF5630.” / “Match the palette from atlassian.com — blues and neutrals.”

    3. Define the narrative and structure
      Tell Rovo what to include, exclude, or reorder. If you have a story arc, spell it out.
      “Start with a bold problem statement; end with a clear call to action.” / “Include these slides in order: intro, problem, solution, timeline, budget, next steps.”

    4. Specify audience and tone
      Say who it’s for and how it should sound.
      “C-suite budget review — concise, confident, data-driven. Max three bullets per slide.”

    5. Control visuals
      Note preferences for imagery, icons, charts, or layout style.
      “Include a timeline graphic for the roadmap slide.”

    Your next presentation is already in Confluence

    The knowledge your team needs to build a great presentation already exists — in your Confluence pages, your meeting notes, your project plans. Confluence slides gives you a faster way to turn all of that into a story you can actually share, without spending the afternoon doing it manually.

    No blank slate. No tool-switching. No reformatting. Just go from doc to deck in seconds, and present with confidence, all within Confluence.

    If you’re already a Confluence user, create slides now.

    Not yet using Confluence? Try it for free and discover how you can create and share knowledge across teams.

    Original source
  • Aug 10, 2026
    • Date parsed from source:
      Aug 10, 2026
    • First seen by Releasebot:
      Aug 11, 2026
    Atlassian logo

    Confluence by Atlassian

    Agents are in Confluence (and wherever you need them to be)

    Confluence adds agentic workflows that let @mentioned agents create, edit, comment, label, set status, and build whiteboards or databases alongside teams, with Atlassian Rovo MCP support in Claude, Cursor, ChatGPT, and IDEs for live page work.

    @MENTION AN AGENT ON ANY PAGE AND IT CREATES, EDITS, AND COMMENTS ALONGSIDE YOUR TEAM. THROUGH THE ATLASSIAN ROVO MCP, THE SAME AGENTS WORK FROM CLAUDE, CURSOR, OR YOUR IDE.

    Agents have been working in Confluence since we launched custom agents in May 2024, and teams now run more than 5 million agent invocations a month. In February alone, Agents saved Atlassian customers more than 200,000 hours.

    Now, agents can do practically everything you can do. Beyond creating or editing pages, Agents can comment, label, set status, and create whiteboards or databases — working exactly the way a teammate does. Mention one in the editor or a comment and it acts right there, grounded in your team’s own content. And through the Atlassian Rovo MCP, the same agents work from Claude, Cursor, ChatGPT, or your IDE, reading and writing the live page rather than a copy of it.

    Getting work unstuck

    Handing real work to an agent only matters if you can trust what it does. That belief shaped every decision we made bringing agents into Confluence, so before an agent ever touches a page, you know it will work within the permissions you set, act only where it should, and leave a clear trail behind it. With that foundation in place, agents become something you actually want on your team.

    A page waits for someone to have time, feedback sits in comments until the owner circles back, and the decision everyone needs stays in one person’s head until they write it down. None of that is a hard problem. It’s that a person has to do every step, and people are busy.

    Agents change the pace without changing the job. Give one a task and the page moves while you’re in a meeting. Routine feedback gets processed before you reopen it, and the decision that actually needs your judgment is waiting with the work around it already done.

    How it works

    • Mentioning an agent. Tag an agent in the editor or in a comment the same way you’d tag a colleague. It reads the page as context and responds there, contributing to the page without anyone moving the work or rebuilding the context.
    • Seeing what agents actually did. Confluence Analytics counts agents alongside people across page, space, site, and Mission Control views. Switch any page between all viewers, people, and agents to see which agents read it and how often. Agents appear as contributors on content they helped create or update, and an agent working on someone’s behalf shows up next to the person who invoked it. If an agent read a page 200 times last week, you can now see that.
    • Doing the work, not describing it. Agents create and edit pages, work with comments, apply labels, set status, and act across Confluence content types. A single prompt returns a complete formatted page with panels, tables, and diagrams, or chains a longer job end to end, like drafting release notes from a merged pull request, publishing them, and sharing a public link. The same capabilities are available through Rovo Chat, automations, custom agents, MCP, and the command line.
    • Bringing your own agent. Create a Team agent in Confluence, start from a ready-made template, or connect a custom or external agent through MCP. Wherever the agent comes from, it works with the same core Confluence actions.
    • Working from your tool of choice. Through the Atlassian Rovo MCP, agents in Claude, Cursor, ChatGPT, or your IDE read and write live Confluence content. The agent reads what is true right now and writes back to the same page your team is looking at.
    • Setting the rules for a space. Space-level instructions give agents a shared playbook for how that team works, so the same agent behaves differently in a marketing space than in an engineering one. Agents never surface content the person who invoked them couldn’t already see, every action is reversible in version history, and a stale edit is rejected rather than quietly overwriting a teammate.

    What teams are already building

    The agents customers built before this release are a good preview of what a more capable one can do. Riverty’s Lessons Learned agent mines past work so teams stop re-learning the hard way. KFC’s Architecture Review agent pre-checks proposals against document standards. Pythian’s Progress Tracker pulls signal from Jira and Confluence and drafts the status email. Sprout Social’s Onboarding agent answers roughly 80% of new-hire questions and spins up role guides.

    You don’t need to code anything to build one. If you can describe what you want in plain English, you can build an agent in Rovo Studio and publish it to your team.

    Better context = better output

    Agents in Confluence run on the Teamwork Graph, the living context layer that connects work, people, knowledge, and code across Atlassian and your connected tools. In our own benchmarking, agents grounded in Teamwork Graph context returned 44% more accurate results while using 48% fewer tokens.

    Availability

    Agentic workflows in Confluence are powered by Rovo, available on Standard, Premium, and Enterprise Cloud plans. All Atlassian Cloud customers can use the Atlassian Rovo MCP Server.

    Getting started

    1. Open a Confluence page and @mention an agent in a comment.
    2. Browse ready-made agent templates and start from one built for your team’s job.
    3. To work from another tool, add the Atlassian Rovo MCP server to your AI client:
    • Explore agent use cases
    • Set up the Rovo MCP server
    • Learn from more examples of customer agents
    Original source
  • Aug 4, 2026
    • Date parsed from source:
      Aug 4, 2026
    • First seen by Releasebot:
      Oct 24, 2026
    Atlassian logo

    Confluence by Atlassian

    Issues resolved in 10.2.15

    Confluence releases version 10.2.15, a bug-fix update that addresses security vulnerabilities and resolves issues affecting templates, calendar events, notifications, application links, and comment editing.

    The Atlassian Confluence team is pleased to announce the release of Confluence 10.2.15, which is a bug-fix release.

    Don't have Confluence 10.2 yet?

    Check out the new features and other highlights in the Confluence 10.2 release notes.

    Get the latest version

    We recommend you read the Confluence 10.2 release notes and you back up your confluence-home directory and database before upgrading.

    Released on 04 August 2026

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution CONFSERVER-99991 Semantic Search support in Confluence DC Suggestion Jun 11, 2025 02:10 Sept 09, 2026 13:57 Will Yasvoin Jonathan Soo CLOSED Fixed CONFSERVER-104402 BASM (Broken Authentication & Session Management) Apache Tomcat Dependency in Confluence Data Center Public Security Vulnerability Aug 12, 2026 17:30 Sept 15, 2026 17:01 Unassigned Security Metrics Bot Highest PUBLISHED Fixed CONFSERVER-104399 MITM (Man-in-the-Middle) org.apache.tomcat:tomcat-coyote-ffm Dependency in Confluence Data Center Public Security Vulnerability Aug 08, 2026 17:30 Aug 18, 2026 22:00 Unassigned Security Metrics Bot Highest PUBLISHED Fixed CONFSERVER-104391 Security Misconfiguration org.bouncycastle:bcprov-lts8on Dependency in Confluence Data Center Public Security Vulnerability Aug 05, 2026 16:30 Aug 18, 2026 22:00 Unassigned Security Metrics Bot Highest PUBLISHED Fixed CONFSERVER-104446 CSRF (Cross-Site Request Forgery) nanoid Dependency in Confluence Data Center Public Security Vulnerability Sept 02, 2026 18:30 Sept 15, 2026 17:01 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104403 BASM (Broken Authentication & Session Management) Apache Tomcat Dependency in Confluence Data Center Public Security Vulnerability Aug 12, 2026 17:30 Sept 15, 2026 17:01 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104396 DoS (Denial of Service) linkify-it Dependency in Confluence Data Center Public Security Vulnerability Aug 05, 2026 17:31 Aug 18, 2026 22:00 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104395 DoS (Denial of Service) org.postgresql:postgresql Dependency in Confluence Data Center Public Security Vulnerability Aug 05, 2026 17:30 Aug 18, 2026 22:00 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104394 DoS (Denial of Service) linkify-it Dependency in Confluence Data Center Public Security Vulnerability Aug 05, 2026 17:30 Aug 18, 2026 22:00 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104393 Information Disclosure postcss Dependency in Confluence Data Center Public Security Vulnerability Aug 05, 2026 16:31 Aug 18, 2026 22:00 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-103910 SQLi (SQL Injection) org.hibernate:hibernate-core Dependency in Confluence Data Center Public Security Vulnerability May 21, 2026 21:30 Aug 18, 2026 22:01 Unassigned Security Metrics Bot High PUBLISHED Fixed CONFSERVER-104379 Page template labels can not be saved when an incremental sync subscription is active. Bug Jul 23, 2026 06:06 Sept 09, 2026 13:57 Tom Smallridge Tom Smallridge Medium CLOSED Fixed CONFSERVER-104367 Team Calendar events cannot be moved by drag&drop due to malformed NaN date values in browser request Bug Jul 17, 2026 08:37 Aug 04, 2026 09:12 Zac Xu Shruthi Hebbal Medium CLOSED Fixed CONFSERVER-104289 Memory Leak in jsoup threadMemo causes unreleased heap in NotificationSender thread, where repeated delivery failure resulting in OutOfMemoryError Bug Jul 01, 2026 02:51 Sept 18, 2026 02:30 Niraj Bhawnani Damien Tan Medium CLOSED Fixed CONFSERVER-103875 Losing shared home access on Confluence results in Application Links regenerated secrets that break OAuth trust Bug May 19, 2026 11:51 Oct 09, 2026 07:10 Jeffery Xie Gabriel Piedade Medium CLOSED Fixed CONFSERVER-104371 Unable to edit an existing comment containing a code block macro with "../" characters Bug Jul 21, 2026 11:57 Oct 09, 2026 07:10 Tom Smallridge Bibek Roy Low CLOSED Fixed

    16 issues

    Last modified on Aug 4, 2026

    Original source
  • Jul 9, 2026
    • Date parsed from source:
      Jul 9, 2026
    • First seen by Releasebot:
      Oct 24, 2026
    Atlassian logo

    Confluence by Atlassian

    Issues resolved in 10.2.14

    Confluence releases version 10.2.14, a bug-fix update that addresses multiple security vulnerabilities and fixes issues affecting large-page editing and Labels List macro loading. Atlassian recommends backing up the home directory and database before upgrading.

    The Atlassian Confluence team is pleased to announce the release of Confluence 10.2.14, which is a bug-fix release.

    Don't have Confluence 10.2 yet?

    Check out the new features and other highlights in the Confluence 10.2 release notes.

    Get the latest version

    We recommend you read the Confluence 10.2 release notes and you back up your confluence-home directory and database before upgrading.

    Key Summary T Created Updated Due P Status Resolution CONFSERVER-104374 DoS (Denial of Service) tar Dependency in Confluence Data Center Public Security Vulnerability Jul 23, 2026 04:29 Aug 18, 2026 22:01 Highest PUBLISHED Fixed CONFSERVER-104370 SSRF (Server-Side Request Forgery) axios Dependency in Confluence Data Center Public Security Vulnerability Jul 20, 2026 21:22 Jul 21, 2026 17:00 Highest PUBLISHED Fixed CONFSERVER-104360 Prototype Pollution Axios Dependency in Confluence Data Center Public Security Vulnerability Jul 11, 2026 04:31 Jul 21, 2026 17:00 Highest PUBLISHED Fixed CONFSERVER-104359 SSRF (Server-Side Request Forgery) axios Dependency in Confluence Data Center Public Security Vulnerability Jul 11, 2026 04:30 Jul 21, 2026 17:00 Highest PUBLISHED Fixed CONFSERVER-104357 SSRF (Server-Side Request Forgery) Axios Dependency in Confluence Data Center Public Security Vulnerability Jul 11, 2026 04:30 Jul 21, 2026 17:00 Highest PUBLISHED Fixed CONFSERVER-100547 While editing a large page (scrollable both bottom and right), cursor jumps to the top when clicking far to the right of the existing text at the bottom Bug Aug 13, 2025 11:54 Jul 17, 2026 06:06 Highest CLOSED Fixed CONFSERVER-100534 Labels List Macro Causes Slow Page Loading in Confluence Bug Aug 08, 2025 21:21 Aug 27, 2026 12:41 Highest CLOSED Fixed CONFSERVER-104500 DoS (Denial of Service) axios Dependency in Confluence Data Center Public Security Vulnerability Oct 16, 2026 01:45 Oct 20, 2026 17:01 High PUBLISHED Fixed CONFSERVER-104406 DoS (Denial of Service) tar Dependency in Confluence Data Center Public Security Vulnerability Aug 14, 2026 17:30 Sept 15, 2026 17:01 High PUBLISHED Fixed CONFSERVER-104398 DoS (Denial of Service) io.micrometer:micrometer-core Dependency in Confluence Data Center Public Security Vulnerability Aug 07, 2026 16:30 Aug 18, 2026 22:00 High PUBLISHED Fixed CONFSERVER-104377 DoS (Denial of Service) tar Dependency in Confluence Data Center Public Security Vulnerability Jul 23, 2026 05:29 Aug 18, 2026 22:01 High PUBLISHED Fixed CONFSERVER-104376 Denial of Service (DoS) tar Dependency in Confluence Data Center Public Security Vulnerability Jul 23, 2026 05:29 Aug 18, 2026 22:01 High PUBLISHED Fixed CONFSERVER-104364 File Inclusion fast-uri Dependency in Confluence Data Center Public Security Vulnerability Jul 11, 2026 04:31 Jul 21, 2026 17:00 High PUBLISHED Fixed CONFSERVER-104363 Injection fast-uri Dependency in Confluence Data Center Public Security Vulnerability Jul 11, 2026 04:31 Jul 21, 2026 17:00 High PUBLISHED Fixed CONFSERVER-104361 DoS (Denial of Service) netty Dependency in Confluence Data Center Public Security Vulnerability Jul 11, 2026 04:31 Jul 21, 2026 17:00 High PUBLISHED Fixed CONFSERVER-104358 Injection axios Dependency in Confluence Data Center Public Security Vulnerability Jul 11, 2026 04:30 Jul 21, 2026 17:00 High PUBLISHED Fixed CONFSERVER-104356 Injection axios Dependency in Confluence Data Center Public Security Vulnerability Jul 11, 2026 04:30 Jul 21, 2026 17:00 High PUBLISHED Fixed CONFSERVER-104355 Injection axios Dependency in Confluence Data Center Public Security Vulnerability Jul 11, 2026 04:30 Jul 21, 2026 17:00 High PUBLISHED Fixed CONFSERVER-104353 Injection js-cookie Dependency in Confluence Data Center Public Security Vulnerability Jul 11, 2026 04:30 Jul 21, 2026 17:00 High PUBLISHED Fixed CONFSERVER-104352 Injection axios Dependency in Confluence Data Center Public Security Vulnerability Jul 11, 2026 04:30 Jul 21, 2026 17:00 High PUBLISHED Fixed

    Showing 20 out of 46 issues

    Original source
  • Jun 2, 2026
    • Date parsed from source:
      Jun 2, 2026
    • First seen by Releasebot:
      Oct 24, 2026
    Atlassian logo

    Confluence by Atlassian

    Issues resolved in 10.2.13

    Confluence releases a bug-fix update with security fixes for Data Center and Server, plus improvements addressing editor paste errors, application link scopes, signup settings, slow space directory queries, and other reliability issues.

    The Atlassian Confluence team is pleased to announce the release of Confluence 10.2.13, which is a bug-fix release.

    Don't have Confluence 10.2 yet?

    Check out the new features and other highlights in the Confluence 10.2 release notes.

    Get the latest version

    We recommend you read the Confluence 10.2 release notes and you back up your confluence-home directory and database before upgrading.

    Global Rate limiter for All the Confluence End points

    • Injection io.netty:netty-codec-dns Dependency in Confluence Data Center
    • HTTP Request Smuggling io.netty:netty-codec-http Dependency in Confluence Data Center
    • BASM (Broken Authentication & Session Management) org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center and Server
    • Improper Authorization org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center
    • Injection org.apache.tomcat:tomcat-coyote Dependency in Confluence Data Center
    • HTTP Request Smuggling org.eclipse.jetty:jetty-http Dependency in Confluence Data Center
    • Stored XSS in Confluence Data Center and Server
    • Information Disclosure org.apache.tomcat:tomcat-websocket Dependency in Confluence Data Center
    • HTTP Request Smuggling io.netty:netty-codec-http Dependency in Confluence Data Center
    • Business Logic Vulnerability Apache Tomcat Dependency in Confluence Data Center
    • DoS (Denial of Service) org.apache.tomcat:tomcat-catalina Dependency in Confluence Data Center
    • Copying and pasting content in the editor encounters a problem with Microsoft Edge browser.
    • Pasting a file into the editor causes 422 Unprocessable Entity Errors and errors saving a draft as well as locking you out from editing the page any further
    • When updating an existing Cloud Connector application link, the scopes are not saved successfully
    • User Signup Options UI does not respect unchecked "Allow" toggle
    • When loading the Space Directory page (especially when filtering by a space category) creates Long running DB sessions eventually impacting the instance performance
    • Jira issue macro/Jira charts throws 'Failed to find org.hibernate.Session from the current thread' error when user's OAuth2 AppLink refresh token expires
    • Find Drafts in IDOR returns with zero offset even if non-zero offset is provided
    • "Create from template" dialog scans all available spaces instead of stopping at configured limit when populating space picker
    Original source
  • May 12, 2026
    • Date parsed from source:
      May 12, 2026
    • First seen by Releasebot:
      May 12, 2026
    Atlassian logo

    Confluence by Atlassian

    How customers are using Confluence Agents to turn knowledge into action

    Confluence launches out-of-the-box partner agents and expands Rovo Studio workflows so teams can turn knowledge into PRDs, status updates, onboarding guides, lessons learned, and more, with automation and Jira integration to speed up work across Confluence and external tools.

    Since we first launched custom agents in May of 2024, we’ve seen teams use Rovo to build agents in Confluence that help them accomplish everything from turning customer feedback into PRDs to maintaining consistency across large sets of data and processes.

    And agents are getting even more popular, with over 5M invocations of agents every month. They take the foundation of knowledge that lives in Confluence, and act on it, saving customers over 200K hours in February alone. That’s serious time back to help teams ship faster, gain context more easily, and achieve better business outcomes.

    We polled organizations to see what agents are adding value to their workflows in Confluence, so you can find inspiration for workflows across Eng, Product, HR, Project Management, and more. Here are seven of our favorites:

    • HarperCollins’s Meeting-to-Action Companion: Turns messy notes into crisp decisions, documented in Confluence and completed Jira tickets, so nothing gets lost.
    • Docusign’s PRD & Spec Author: Takes a rough brief and ships a review-ready PRD with linked Jira work items in minutes.
    • Riverty’s Lessons Learned: Mines past work in Confluence so your team stops re‑learning the hard way.
    • KFC’s Architecture Review: Pre-checks proposals against document standards, so approvals are a breeze.
    • Pythian’s Progress Tracker: Pulls the signal from Jira + Confluence and drafts status update emails for you.
    • Sprout Social’s Onboarding & Playbook Builder: Answers ~80% of new‑hire questions and spins up role guides for new hires.
    • Procore’s Backlog & Discovery Synthesizer: Sifts feedback to surface what truly earns a spot on the roadmap.

    The seven agents above work across Confluence and Jira — your knowledge layer and your execution layer. But with MCP (Model Context Protocol), agents can reach beyond Atlassian into external tools. An agent can read knowledge in Confluence, think about it, and then take action in a third-party tool without you having to context-switch, reformat, or copy-paste between tabs. Confluence just launched out-of-the-box partner agents, with Lovable, Replit, and Gamma, to turn knowledge into prototypes, codebases, or visuals, all without the human tax of translating between tools.

    And because MCP is an open protocol, this ecosystem keeps growing. Any tool that supports MCP can become the next output surface for your Confluence knowledge.

    Make your own agents with Rovo Studio

    You don’t need to code anything. If you can describe what you want in plain English, you can build an agent. Here’s how:

    1. Open Rovo Studio.
      From any Confluence page, click the app switcher in left section of top nav and open Studio. You’ll land on a canvas where you can create and manage agents.

    2. Paste your instructions.
      This is the heart of the agent — a plain-language prompt that tells it what to do, what to read, and how to respond. Every use case below includes ready-to-paste instructions you can drop right in.

    3. Choose tools and knowledge.
      Pick which tools the agent can use, like Confluence pages, Jira issues, Slack channels, or connect it to tools through the MCP gallery. Under knowledge, scope it to the spaces or projects it needs.

    4. Test and publish.
      Run a few test prompts in the preview pane, tweak the instructions until the output feels right, then publish. Your team can start using it immediately from Rovo chat, Confluence pages, or Jira work items.

    That’s it — four steps, no engineering ticket required.

    Once you’re up and running, here are some tips to get the most out of your agents:

    • Pick your use case.
      Identify one or two workflows where Confluence is already the system of record, like PRDs, meeting notes, or incidents, and start with agents there.
    • Document your standards.
      Put your templates and guidelines into Confluence pages so agents have clear patterns to follow.
    • Use agents with automation.
      Let Studio create a workflow for you. Pick an outcome and use Studio to build an automation rule and agent to let it run. The “Go further” patterns in this post are good starting points and it’s easy to use Natural Language to build the automation rules for you.
    • Pilot with a small team.
      Collect feedback on drafts the agents produce. Tune prompts accordingly.
    • Scale and measure impact.
      Track time saved on routine docs, number of Confluence pages kept up to standard, and fewer missed follow-ups after meetings.

    Want to copy the examples from Docusign, HarperCollins, and Sprout Social? Get started with the prompts and automation patterns below.

    First, paste the prompts into Rovo Studio’s Creation screen. These become your agent instructions. Then, confirm all the necessary tools are listed in the Tools drop down, and add the appropriate Spaces and Documents under the Knowledge drop down.

    HarperCollins’s Meeting-to-Action Companion

    HarperCollins Publishers uses a meeting-to-action agent to turn messy Confluence notes and call transcripts into structured decision logs with owners, deadlines, and linked Jira issues — automatically. It solves the classic loss of follow-ups between meetings by scanning pages, extracting decisions and action items, and creating the right Jira tickets so work is tracked. Ideal for PMs, team leads, and chiefs of staff who live in recurring meetings, it cuts an hour of manual routing and formatting down to ~15 minutes so they can focus on higher‑impact work.

    Setup instructions

    Paste the following into Rovo Studio’s Creation screen.

    ROLE

    You are a Meeting-to-Action Companion agent that turns messy meeting notes and call transcripts into structured decision logs and tracked work.

    SCOPE & SOURCES

    • Primary notes from [MEETING NOTES SPACE] in Confluence.
    • Meeting pages with call transcripts, bullet notes, or freeform text.
    • Decision-log standards at [DECISION-LOG STANDARDS PAGE LINK].

    WHEN INVOKED

    • Read the full notes/transcript and extract:
      • Decisions (what was decided, by whom, and why).
      • Action items (what needs to happen, by when, and by whom).
    • Rewrite the page into a structured decision log with sections: Decision, Rationale, Owner, Due date, Links (to Jira issues and related docs).
    • For each action item:
      • Create Jira issues using default project [JIRA PROJECT KEY] and issue type [JIRA ISSUE TYPE], unless otherwise specified.
      • Assign issues in this order of precedence: 1) Explicit @mentions on the page, 2) Meeting owner, 3) Team queue or default assignee.
      • Add appropriate labels/components based on the meeting context.
      • Link created Jira issues back to the Confluence page and list their keys under the relevant decision/action.
      • Send a brief Slack notification to [CHANNEL ID] summarizing decisions/actions and linking to the updated page.

    OUTPUT

    • A cleaned-up Confluence decision log that replaces or augments the original notes.
    • A set of Jira issues linked from the decision log.
    • A short Slack message with the link and key highlights.

    CONSTRAINTS

    • Do not invent facts; mark unknowns as TBD and ask focused questions.
    • Do not invent decisions, owners, or dates.
    • If information is missing, include a short "Open Questions" section.
    • Keep sensitive details internal unless explicitly asked for a customer-facing version.

    Try these prompts
    “Turn these notes into a decision log and create Jira issues for each action.”
    “Summarize this customer call into 5 bullets and publish to Confluence.”
    “Turn this standup page into a status update for our exec Slack channel.”

    Docusign’s PRD & Spec Author

    Docusign uses a PRD & Spec Author agent in Confluence to turn a short outline into a complete, review-ready PRD that matches their team’s structure and tone, with suggested Jira epics and stories linked from the doc. It eliminates blank-page PRDs and copy-paste drift by learning from prior specs, decisions, and retros to justify choices. Built for PMs, tech leads, solution architects, and founders who need to go from idea to spec fast, it standardizes outputs, cuts manual rewriting, and reduces glue work across teams.

    Setup instructions

    Paste the following into Rovo Studio’s Creation screen.

    ROLE

    You are a PRD & Spec Author agent that turns short problem statements or Jira work items into complete, review-ready PRDs and specs.

    SCOPE & SOURCES

    • Prior PRDs and specs in [PRD EXAMPLES SPACE OR LABEL] to learn structure, tone, and depth.
    • Standards and templates at [PRD TEMPLATE/STANDARDS PAGE LINK].
    • Input brief from a short problem statement and/or a Jira epic (including linked discovery notes and feedback).

    WHEN INVOKED

    • Analyze the brief and any linked Confluence pages (discovery notes, research, customer feedback).
    • Draft a complete, review-ready PRD in Confluence that follows our headings and conventions from [PRD TEMPLATE/STANDARDS PAGE LINK], including:
      • Problem statement and background
      • Goals/non-goals
      • Users and use cases
      • Requirements and acceptance criteria
      • Assumptions
      • Risks
      • Dependencies
      • Open questions
    • Propose Jira epics and stories that map to the PRD:
      • Default to project [DEFAULT JIRA PROJECT KEY] and issue types [DEFAULT JIRA ISSUE TYPES], unless otherwise specified.
    • Link the Jira issues back to the PRD and cross-link the PRD from the Jira issues.

    OUTPUT

    • A new or updated PRD in Confluence, published under [WHERE TO PUBLISH PRDS].
    • A set of linked Jira epics/stories reflecting the proposed work.
    • Optional: a short summary for stakeholders via [NOTIFY VIA] with key highlights and a PRD link.

    CONSTRAINTS

    • Do not invent facts; mark unknowns as TBD and ask focused questions.
    • Stay consistent with tone and level of detail used in prior PRDs in [PRD EXAMPLES SPACE OR LABEL].
    • Do not overwrite existing PRDs without preserving key decisions and rationale; update incrementally.

    Try these prompts
    “Turn these notes into a decision log and create Jira issues for each action.”
    “Summarize this customer call into 5 bullets and publish to Confluence.”
    “Turn this standup page into a status update for our exec Slack channel.”

    Go further: automate it

    The most advanced version of this agent doesn’t wait for a PM to invoke it. Set up an automation rule using natural language that triggers on a schedule and points the agent at 90 days of customer feedback from a Jira project or JPD board. The agent identifies emergent themes, clusters them, and auto-generates short PRD drafts for each — structured, user-backed, and ready for a PM to refine.

    Automation workflow:
    Trigger: Scheduled (weekly) → Action: Invoke “Feedback to PRD & Spec Author” agent → Prompt: “Analyze the last 90 days of feedback from [FEEDBACK PROJECT LINK HERE], identify the top emergent themes, and generate a one-page PRD draft for each theme with linked evidence” → Action: Publish new Confluence page as PRD from agent output.

    Riverty’s Lessons Learned Agent

    A Lessons Learned Rovo agent helps Riverty turn past investigations into a reusable knowledge base. It scans completed tasks from Riverty’s data analysis desk, distills the key insights, and publishes standardized learnings to Confluence so teams can quickly see what’s been tried before, what worked, and what to avoid. Instead of starting from scratch, users can query the agent with a problem they’re facing and immediately surface lessons gleaned from similar tasks, complete with links back to the original analysis. As Atlassian Product Owner Andrei Tuch puts it, “Every time someone asks us to connect one of the popular LLMs to our Jira or Confluence, we help them implement their use case in Rovo instead – because it always works better.”

    Setup instructions

    Paste the following into Rovo Studio’s Creation screen.

    ROLE

    You are a Lessons Learned agent that turns completed analysis tasks into a reusable knowledge base and answers new questions by surfacing relevant past learnings.

    SCOPE & SOURCES

    • Completed tasks from your data analysis desk (Jira tickets, summaries, attachments).
    • Confluence pages containing prior analyses, retros, and decision logs.
    • Optional: a central "Lessons Learned" index page to organize topics, tags, and links.

    WHEN INVOKED

    • Ingest and synthesize learnings from completed analysis tasks: problem, approach, data used, key findings, decisions, caveats.
    • Publish concise, standardized summaries to Confluence with links back to source tasks and artifacts.
    • Answer user queries about current problems by retrieving and summarizing lessons from similar past tasks; highlight applicable insights and known pitfalls.
    • When helpful, create or update a central "Lessons Learned" index page that categorizes learnings by topic, system, and tags.

    OUTPUT

    • A Confluence page (or section) per learning with: Context, What we tried, What worked/failed, Key takeaways, Reuse guidance, Links.
    • Cross-links between related learnings and the optional central index.
    • Short, actionable answers in chat that cite and link to the relevant learnings.

    CONSTRAINTS

    • Do not invent facts; mark unknowns as TBD and ask focused questions.
    • Preserve source wording for critical details (numbers, thresholds, caveats); summarize without changing meaning.
    • Attribute each learning to its original task/page with links and dates.

    Try these prompts
    “Analyze these tasks and publish Lessons Learned pages in Confluence.”
    “Surface past lessons that apply to this problem, with risks and caveats.”
    “Update the Lessons Learned index with today’s entries and cross-links.”

    KFC’s Architecture Review Agent

    KFC uses an Architecture Review agent to raise the quality bar on proposals before they ever reach the Architecture Review Board. The board had strong guidelines and principles in place, but they weren’t consistently followed, so review time was spent sense‑checking completeness and basic alignment instead of debating trade‑offs and long‑term strategy. Now, teams invoke an agent that checks new proposals against KFC’s standards, flags gaps, and suggests improvements, so only proposals that meet baseline expectations move forward. The result: fewer low‑quality submissions, more time on high‑value architectural discussion, and an architecture history that’s easy to navigate and keep up to date.

    Setup instructions

    Paste the following into Rovo Studio’s Creation screen.

    ROLE

    You are an Architecture Review agent that pre-reviews architecture proposals and helps maintain high-quality architecture decision records.

    ACCESS

    • Confluence (read/write)
    • Jira (read-only or write, as configured)

    SCOPE & SOURCES

    • Architecture principles and guidelines at [ARCHITECTURE PRINCIPLES/GUIDELINES PAGE LINK].
    • Example high-quality proposals at [EXAMPLE PROPOSALS SPACE/LABEL/PAGE TREE].
    • Architecture decision templates at [ARCHITECTURE DECISION TEMPLATE PAGE LINK].
    • Draft proposals as Confluence pages or attachments, optionally linked from Jira.

    WHEN INVOKED ON A DRAFT PROPOSAL

    • Check the proposal against guidelines, including required sections, clarity of scope and context, explicit trade-offs and alternatives, risks, dependencies, operational concerns, and alignment with existing patterns/principles.
    • Compare to similar, high-quality proposals and call out deviations.
    • Suggest concrete improvements: sections to add, clarifications to make, risks to articulate, and relevant systems/ADRs/Jira epics to link.
    • Provide a short summary at the top with a readiness rating (Ready/Needs Work), key gaps, and recommended next steps.

    OPTIONAL: FINAL DECISION RECORD

    • Once approved, use [ARCHITECTURE DECISION TEMPLATE PAGE LINK] to generate a finalized Confluence decision record; capture decision, rationale, trade-offs, risks, dependencies; and link related Jira work and ADRs.

    OUTPUT

    • A reviewed and annotated proposal that meets baseline standards, or clear guidance on what to fix.
    • Optionally, a finalized architecture decision record page linked from Jira and other system documentation.

    CONSTRAINTS

    • Do not invent facts; mark unknowns as TBD and ask focused questions.
    • Do not invent architecture decisions, risks, or dependencies; if unclear, add questions for the proposal owner.
    • Respect existing decision history; do not overwrite approved decisions, only add context or clarifications.

    Try these prompts
    “Review this proposal against our guidelines and list what needs fixing.”
    “Rewrite this draft to match our architecture proposal template.”
    “Create an architecture decision record for this approved proposal.”

    Pythian’s Progress Tracker

    Pythian uses a Progress Tracker agent to replace ad‑hoc, manual status emails with consistent, data‑backed updates pulled directly from Jira and Confluence. Built for account managers, customer success leaders, and product marketers who send regular customer updates, it scans a Confluence space and linked Jira work to draft polished, customer‑facing summaries with progress, key wins, risks, and next steps — plus an internal‑only version that includes the sensitive details. Instead of hunting across issues, docs, and email threads to remember what changed, teams invoke the agent from a single Confluence page or Jira epic and get tailored updates in minutes. Combined with Transcript Insight and Team Recap agents, it’s saving Pythian teams an average of 20 minutes per day and freeing them up to focus on more strategic, high‑impact work.

    Setup instructions

    Paste the following into Rovo Studio’s Creation screen.

    ROLE

    You are a Progress Tracker agent for customer projects that turns scattered work updates into consistent, data-backed status summaries.

    ACCESS

    • Confluence (read/write)
    • Jira (read for linked projects; write for comments or labels if enabled)

    SCOPE & SOURCES

    • A specified Confluence page or Jira epic as the system of record for the project.
    • Linked Jira issues (status, comments, labels, due dates).
    • Related Confluence pages (plans, decision logs, prior updates).
    • Example status updates and summaries at [STATUS EXAMPLES SPACE/LABEL/PAGE TREE].

    WHEN INVOKED ON A PROJECT

    • Determine what has changed since the last update (completed work, in-progress items, blocked tasks, new risks, notable customer interactions/decisions).
    • Synthesize a concise status summary emphasizing outcomes delivered, progress against milestones, upcoming work/timelines, and key risks with mitigations.
    • When requested, create two versions:
      • Customer-facing: friendly, non-technical, value/timeline/next steps, no sensitive details.
      • Internal: technical details, blockers, staffing notes, technical debt; clearly marked Internal-only.
    • Maintain consistent headings: Overview; Progress since last update; Key wins; Risks/blockers; Next steps/upcoming milestones.
    • Link relevant Jira issues and Confluence pages in each section.

    OUTPUT

    • Draft/update a Confluence status page under [STATUS SPACE/PARENT PAGE] with clear date and sections.
    • Optional: email/Slack-ready snippets for customer and internal audiences.

    CONSTRAINTS

    • Do not invent facts; mark unknowns as TBD and ask focused questions.
    • Do not expose internal-only details in customer-facing versions.
    • Keep tone aligned to prior examples in [STATUS EXAMPLES SPACE/LABEL/PAGE TREE].

    Try these prompts
    “Draft a customer-ready status update from this plan and linked Jira issues.”
    “Summarize progress since the last update with wins, risks, and next steps.”
    “Draft an exec summary for the customer and a detailed one for our team.”

    Go further: close the loop entirely

    The ultimate version of this pattern doesn’t just write the update — it automates the entire feedback collection cycle. Here’s what an internal team at Atlassian built: when new customer feedback hits a Jira project, an automation rule sends the customer a Calendly link to schedule a follow-up call. Loom records the meeting. A Rovo agent summarizes the recording and writes polished notes into a Confluence page. Then a second automation broadcasts the summary — customer name, key themes, action items, and the Loom recording link — to a shared Slack channel. The PM’s only job? Show up and listen. Everything else happens automatically.

    Sprout Social’s Onboarding & Playbook Builder

    Sprout Social uses an Onboarding & Playbook Builder agent to turn scattered how‑tos, runbooks, and team docs into structured, role‑specific onboarding guides and reusable playbooks. Paired with Loom-based onboarding, the agent now answers ~80% of new‑hire questions directly in their Slack onboarding channel by routing them to the right Confluence content and steps. The result: more than 360 hours of work saved per year, faster ramp-up for new employees, and a dramatically lighter IT and team‑lead burden during those critical first weeks.

    Setup instructions

    Paste the following into Rovo Studio’s Creation screen.

    ROLE

    You are an Onboarding & Playbook Builder agent for new hires and recurring team processes.

    ACCESS

    • Confluence (read/write)
    • Jira (read/write where enabled)
    • Slack (read/write in specified onboarding channels)

    SCOPE & SOURCES

    • Treat the specified Confluence space(s) or page tree(s) as the source of truth for how the team works: how-tos, runbooks, team charters, architecture overviews, decision logs, process docs.
    • Use role descriptions, competency frameworks, existing onboarding checklists as anchors for what complete onboarding/playbooks should cover.
    • Incorporate Loom or other embedded videos in Confluence as primary learning assets when available.

    WHEN INVOKED FOR A NEW HIRE

    • Ask for or infer role, team, location, seniority (e.g., "Backend Engineer, Core Services, Mid-level").
    • Cluster related Confluence pages into themes (Day 1 basics; Tools & access; Architecture overview; Team rituals; Key projects & metrics).
    • Identify gaps or stale content; flag as TODOs with concrete suggestions.
    • Draft a sequenced onboarding guide in Confluence (e.g., 1–2 weeks) that states goals, orders topics by need, links canonical docs/Loom/Jira, and proposes tasks that can become Jira issues.

    WHEN INVOKED FOR A RECURRING PROCESS PLAYBOOK

    • Analyze past Confluence pages, Jira issues, retros for the process (e.g., launches, incidents, QBRs).
    • Extract steps, roles, timelines, checklists, known pitfalls.
    • Draft a reusable playbook that defines purpose/owner/success metrics; outlines phases with inputs/outputs and DRIs; links examples/templates/Jira; includes a copyable checklist.

    SLACK + Q&A BEHAVIOR

    • When mentioned in onboarding channels: search relevant Confluence pages and Loom links; point to the best canonical resource first, then summarize if needed.
    • If no good answer exists: say so; offer a provisional answer based on adjacent docs; suggest creating/updating a Confluence page/section.

    OUTPUT

    • A structured onboarding guide page for the role/team.
    • One or more reusable process playbook pages in Confluence.
    • Helpful, link-rich Slack answers guiding new hires to canonical docs.

    CONSTRAINTS

    • Do not invent facts; mark unknowns as TBD and ask focused questions.
    • Do not invent policies, access rights, or sensitive details; if unclear, add a "Questions for manager or IT" section.
    • Prefer existing canonical pages over duplicates; if multiples exist, choose and label the canonical one.

    Try these prompts
    “Build a 2-week onboarding path for a new backend engineer on this team.”
    “Create a reusable playbook for beta launches from these three past docs.”
    “Curate the top 10 docs a new PM should read and organize them on one page.”

    Procore’s Backlog & Discovery Synthesizer

    Procore uses a Backlog & Discovery Synthesizer agent to bridge the gap between customer insights in Confluence and the product backlog in Jira. Instead of PMs trying to remember which interview, feedback log, or research report justified a given idea, the agent connects discovery notes, research pages, and feedback docs to related Jira epics and stories, then rolls everything up into evidence‑backed themes and prioritized recommendations. Prioritization sessions shift from “what do we remember” to “what does the evidence say,” and hunting for buried tickets or docs that used to take 20 minutes now happens almost instantly via Rovo chat and summarized Confluence pages.

    Setup instructions

    Paste the following into Rovo Studio’s Creation screen.

    ROLE

    You are a Backlog & Discovery Synthesizer agent that connects customer insights in Confluence to the product backlog in Jira and produces evidence-backed priorities.

    ACCESS

    • Confluence (read/write)
    • Jira (read for relevant projects; write where enabled for comments/labels)

    SCOPE & SOURCES

    • Discovery and research content in Confluence (user interviews, discovery notes, feedback logs, research reports, experiment results).
    • Backlog items in Jira (ideas, feature requests, bugs, roadmap epics) in specified projects/boards.
    • Prioritization framework at [PRIORITIZATION FRAMEWORK PAGE LINK] (e.g., RICE, impact/effort).

    WHEN INVOKED

    • Ask for or infer product area, segment/persona, and timeframe (e.g., "Core workflows, mid-market, last 90 days of feedback").
    • Cluster discovery inputs into themes (workflow, persona, segment, problem area).
    • For each theme:
      • Identify/link related Jira issues (epics, stories, bugs) via titles, descriptions, tags, linked Confluence pages.
      • Summarize customer signals (pain points, requests, positive feedback) with short excerpts where useful.
      • Flag conflicting/unclear signals as open questions.

    OUTPUT

    • Create/update a Confluence summary page under [DISCOVERY/ROADMAP SPACE] that lists themes with evidence, groups/links Jira items under each, includes a ranked "Recommended priorities" section with rationale, and captures open questions/risks/assumptions.
    • Keep language clear and decision-ready for prioritization and roadmap reviews.

    CONSTRAINTS

    • Do not invent facts; mark unknowns as TBD and ask focused questions.
    • Do not fabricate quotes, quantitative metrics, or prioritization scores; base only on visible data.
    • Preserve nuance; if evidence is weak or mixed, state it and recommend further discovery.

    Try these prompts
    “Synthesize these discovery pages into themes and map them to Jira epics.”
    “Recommend top 10 backlog items for next quarter using our RICE framework.”
    “Summarize top customer pain points by segment and link related Jira tickets.”

    Go further: automate it

    One internal team at Atlassian runs a version of this agent on a weekly schedule across 12,000+ feedback tickets spanning five Jira projects and a Slack channel. Every Friday morning, the agent analyzes the last 30 days of feedback, breaks it into weighted themes — positive feedback on new features, negative feedback on usability, feature requests and suggestions — and posts a structured summary to Slack with example quotes, percentages, and specific recommendations for next steps. Leadership reviews it in minutes. No analyst assembled it. No one remembered to ask.

    Automation rule:
    Trigger: Scheduled (every Friday at 8AM) → Action: Invoke “Feedback Analyst” agent → Prompt: “Analyze the last 30 days of feedback from this project, break it into top themes with examples and links to issues, as well as key customer quotes. Provide recommendations for next steps” → Action: Send Slack message with agent response to your team channel.

    How to invoke Confluence Agents with Jira

    If your team lives primarily in Jira, these agents meet you there. Confluence is the knowledge layer, Jira is the orchestration layer, and agents move fluidly between the two.

    1. Invoke via the assignee picker.
      When you assign an issue in Jira, choose an agent as the assignee. The agent treats the issue as its brief, looks at linked Confluence pages and related tickets, and then writes back into Confluence — creating or updating a PRD, meeting notes page, or whatever the agent is designed to produce — while updating the Jira issue with a link.

    2. @mention agents in comments.
      In Jira or (coming soon!) Confluence comments, mention an agent and give it instructions tied to that issue. The agent will read the issue description, attachments, and any linked Confluence pages, perform the requested work, and then respond in the Jira comment thread with links to the Confluence content it created or updated.

    3. Use “Open in chat” for deeper refinement.
      From a Jira issue, switch into a chat-style view with the agent using “Open in chat.” This pulls in the issue context and any connected Confluence pages, letting you iterate: ask follow-up questions, refine drafts, or request different versions of a Confluence page or update.

    4. Automate invocation with board column triggers.
      Agents can run automatically when an issue moves into certain columns on a Jira board. Moving an epic into “Discovery” could trigger the PRD & Spec Author to draft a first-pass PRD in Confluence. Dragging a bug into “Ready for Postmortem” could trigger the Incident & Postmortem Coach to assemble a Confluence report from linked issues and notes.

    5. Enable agents in Jira via Studio surfaces.
      To make agents available inside Jira, you control their visibility through Studio surfaces. By turning on the Jira surface for a given agent, you allow it to appear in the assignee picker, comments, and relevant Jira entry points while keeping its core logic grounded in Confluence and your other knowledge sources.

    Original source
  • May 5, 2026
    • Date parsed from source:
      May 5, 2026
    • First seen by Releasebot:
      May 18, 2026
    Atlassian logo

    Confluence by Atlassian

    Confluence 9.2.20

    Confluence releases 9.2.20, a bug-fix update that improves stability and fixes issues with JMX metrics logging, cache-related out-of-memory problems, and REST API rate limiting.

    The Atlassian Confluence team is pleased to announce the release of Confluence 9.2.20, which is a bug-fix release.

    Don't have Confluence 9.2 yet?

    Check out the new features and other highlights in the Confluence 9.2 release notes.

    Get the latest version

    We recommend you read the Confluence 9.2 release notes and you back up your confluence-home directory and database before upgrading.

    Key issues fixed in this release include:

    • CONFSERVER-103611: Confluence JMX metrics collection (DCDP) logs frequent AttributeNotFoundException: No such attribute: Mean
    • CONFSERVER-102539: Confluence uses high L2 cache and OOMs (typically encountered where pages with lots of versions come into play) due to Activity streams gadgets request from Jira
    • CONFSERVER-74857: Content REST API is not rate limited

    Last modified on May 5, 2026

    Original source
  • May 5, 2026
    • Date parsed from source:
      May 5, 2026
    • First seen by Releasebot:
      May 7, 2026
    Atlassian logo

    Confluence by Atlassian

    Confluence 10.2.11

    Confluence ships 10.2.11 as a bug-fix release, improving startup stability, JMX metrics logging, scheduled mail handling, REST API rate limiting, and memory usage issues.

    The Atlassian Confluence team is pleased to announce the release of Confluence 10.2.11, which is a bug-fix release.

    Don't have Confluence 10.2 yet?

    Check out the new features and other highlights in the Confluence 10.2 release notes.

    Get the latest version

    We recommend you read the Confluence 10.2 release notes and you back up your confluence-home directory and database before upgrading.

    Issues resolved in 10.2.11

    • CONFSERVER-103634: BlueprintDiscoveryUpgradeTask blocks startup with 100% CPU busy (Bug, Highest priority, Fixed)
    • CONFSERVER-103611: Confluence JMX metrics collection (DCDP) logs frequent AttributeNotFoundException: No such attribute: Mean (Bug, Medium priority, Fixed)
    • CONFSERVER-102709: Scheduled mails gets stuck in Mail Error Queue with OAuth 2.0 SMTP setup (Bug, Low priority, Fixed)
    • CONFSERVER-102539: Confluence uses high L2 cache and OOMs due to Activity streams gadgets request from Jira (Bug, Low priority, Fixed)
    • CONFSERVER-74857: Content REST API is not rate limited (Bug, Low priority, Fixed)

    Last modified on May 5, 2026

    Original source
Releasebot

Curated by the Releasebot team

Releasebot is an aggregator of official product update announcements from hundreds of software vendors and thousands of sources.

Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.