Hello Qlik Users,
In mid-July 2025, a vulnerability was disclosed in the NPM library form-data (GitHub Security Advisory). Qlik became aware of this issue through its standard Secure Development Lifecycle (SDL) processes.
Following an internal review, Qlik R&D and Security teams identified that potentially vulnerable versions of the form-data library were included in some installations of Qlik Sense Enterprise for Windows. However, due to the specific way Qlik utilizes this library, the conditions required for exploitation are not met.
Although the vulnerability was determined to be non-exploitable within Qlik Sense, customers who prefer to upgrade to a version that includes the patched form-data library can do so by installing one of the following releases:
May 2025 Patch 6
November 2024 Patch 18
May 2024 Patch 24
Note: An earlier version of this information was mistakenly published indicating that this CVE was directly related to Qlik Sense for Windows.
Thank you for choosing Qlik,Qlik Global Support
...View More
As HubSpot plans tosunset the v1 contact lists APIonSeptember 30,2025, any API requests using this version forcontacts or listsendpoints will begin to fail after that date. To ensure continuity, Qlik has released a new version,v4,of the connector.
The changes in questions are:
Schema change, primary key, replication key change forcontactsstream
Schema change forcontact_listsstream
What action do I need to take?
Upgrade to the new version. There are two ways to upgrade.
Upgrade and change the schema name
If you do not mind changing the schema name, you can do so by simply creating a newHubSpot integration and deleting the old one.
This is the recommended method. Creating a new integration with a different schema name means you will also benefit from a free historical re-sync of your data.
Upgrade using the same destination schema
If you prefer to reuse the same destination schema name:
Pause the existing integration from their Stitch account.
Wait for any records that arebeing preparedfor loading to be loaded.
Take note of the tables and fields tracked for replication, as well as the replication methods defined for these tables.
Delete the existing integration from your Stitch account.
Drop the schema from your destination data warehouse(or rename it if you'd like to continue working from this data as Stitch completes a new historical replication).
Contact Qlik Stitch Support to coordinate a manual row-usage exemption for this connection.
Configure a new integration with the same name, and Stitch will create this schema in your destination during the loading process.
If you have any questions, we're happy to assist. Contact us using chat or ask similar queries in theQlik Stitch forum.
Thank you for choosing Qlik,Qlik Support
...View More
Description of the Issue
We have identified a degradation in the event auditing functionality in NPrinting, tracked in QCB-32819. Specifically, audit events are not being tracked after a fresh installation of the following versions:
February 2025 SR2
February 2024 SR6
It is important to note that this issue only occurs with new installations of these versions. If the system is upgraded from a previous version, the problem does not manifest.
Effects Observed
Audit events are not being tracked.
The following API endpoints fail with the error:
api/v1/audit/logs
api/v1/audit/events
500 Internal Server Error : An unhandled exception occurred; check the log for more information.
The log file located at %ProgramData%\NPrinting\Logs\nprinting_audit.log shows this error message:
Unable to start Audit service. ERROR: System.AggregateException: One or more errors occurred. ---> System.InvalidOperationException: Could not export the testing database. ---> Npgsql.PostgresException: 42501: permission denied for schema public
Workaround
In addition to performing an upgrade from a previous version instead of a fresh installation, the following steps can be taken to work around the issue:
1. Stop all NPrinting Server services except QlikNPrintingRepoService (otherwise PGAdmin will not find the connection to the DB).
2. Download and install PGAdmin, and connect to the NPrinting Server database.
3. Navigate to the nprinting_audit database and execute the following command:
GRANT ALL PRIVILEGES ON SCHEMA public TO nprinting_audit;
4. Run the following command as administrator:
net start QlikNPrintingAuditService /setup
5. Start all NPrinting server services.
This will allow the audit service to start correctly and resume tracking audit events.
...View More
Salesforce recently identified a security incident involving the Drift app (published by Salesloft). For additional details, see Security Advisory: Unusual Activity in a Third Party Connected App | status.salesforce.com.
Are Qlik customers affected by the security vulnerability?
Qlik does not use the Salesloft Drift application. Although Qlik uses the Salesloft platform, Salesloft has stated there is no evidence of any unusual or malicious activity with the Salesloft platform.
Is Qlik monitoring the situation?
Yes. We are monitoring the situation closely, where the privacy and security of your data are our highest priority.
To stay up to date, review the Salesforce Informational Message ID 20000217: Security Advisory: Unusual Activity in a Third Party Connected App | status.salesforce.com.
Thank you for choosing Qlik, Qlik Support
...View More
Hi everyone, Want to stay a step ahead of important Qlik support issues? Then sign up for our monthly webinar series where you can get first-hand insights from Qlik experts.
Our most recent Techspert Talks session wasQlik Cloud Admin 201.
But wait, what is it exactly?Techspert Talks is a free webinar held on a monthly basis, where you can hear directly from Qlik Techsperts on topics that are relevant to Customers and Partners today.
In this session we will cover:
Troubleshooting entitlement allocation
Exploring Capacity Consumption
Leveraging Qlik APIs for User Management
Watch the recording!
...View More
Don't miss our previous Q&A with Qlik! Pull up a chair and chat with our panel of experts to help you get the most out of your Qlik experience.
Our Qlik expertsheld a Qlik Cloud Migration live Q&A with Qlik webinar, answering all your questions about migration from on-prem to Qlik Cloud and using the tools that are available to make the process easier.
WATCH RECORDING HERE
...View More
Qlik Cloud Governmentand Qlik Cloud Government DoDwill undergo a scheduled system upgrade impactingAutomationsand Backend Databases during the first half of September to improve the continued stability and performance of our platform. Reloads, reports and other workloads referenced by automations may also be impacted during the maintenance window.
When will I be impacted?
This table lists all affected regions and their expected maintenance window. The times are listed in US ET.
Region
Maintenance Window
Qlik Cloud Government
Sept 2 5PM ET - No Downtime
Qlik Cloud Government DoD
Sept 2 5PM ET - No Downtime
Qlik Cloud Government
Sept 8 5PM ET - No Downtime
Qlik Cloud Government DoD
Sept 8 5PM ET - No Downtime
Qlik Cloud Government
Sept 9 5pm ET - 1 Hour Downtime (Automations)
Qlik Cloud Government DoD
Sept 10 5pm ET - 1 Hour Downtime (Automations)
How will I be impacted?
During the scheduled maintenance window, all automations features will be impacted. In addition to the specific impact on automations as specified below, this will also impact reloads, reports and other workloads referenced by automations.
In-product automation pages:The automation pages in the UI will be unavailable, and a service unavailable message will be displayed.
Webhook Triggered Automations:Incoming webhooks from external platforms may be lost during maintenance and the calling system will receive a 429 status code in response. You can resend the internal Qlik Cloud webhooks after the maintenance period has passed from the webhooks page which is accessible from your Administration Console.
Triggered Automations:Any triggered automations sent during the maintenance window will be lost, and a 429 status code will be returned in the response. This includes triggered automations from buttons, external third-party tools, or other use cases relying on this functionality.
Scheduled Automations:Scheduled automations, including those that trigger reloads, reports, or other use cases, will not run during the maintenance window. However, they will automatically restart after the maintenance is completed.
Automations API:The Automations API endpoints will be unavailable during the maintenance window.
Disconnected OAuth app or webhook:In rare cases, too many 429 responses on a webhook or triggered request may cause the requesting system to disconnect the OAuth app or webhook (for webhook automations only), requiring manual reconnection. To reconnect a webhook, disable and re-enable the automation, which will recreate the webhook.
We apologize for any inconvenience this may cause and appreciate your understanding as we work to improve the stability and performance of our platform.
To track updates during the scheduled maintenance, please visit theQlik Cloud Status page. If you encounter unexpected complications during or after the maintenance, contactour Qlik Cloud Government Support inbox: government.support@qlikcloudgov.com. We will be happy to assist you.
Thank you for choosing Qlik,Qlik Support
...View More
Hi everyone, Want to stay a step ahead of important Qlik support issues? Then sign up for our monthly webinar series where you can get first-hand insights from Qlik experts.
The Techspert Talks from August look at Migrating to Qlik Cloud Analytics.
But wait, what is it exactly?Techspert Talks is a free webinar held on a monthly basis, where you can hear directly from Qlik Techsperts on topics that are relevant to Customers and Partners today.
In this session we covered:
Demonstration of the Qlik Cloud Analytics Migration tool
Advantages of Qlik Cloud
SaaS Readiness
Click on this link watch
...View More
Hello Qlik Automate administrators and users,
Based on feedback, Qlik has changed the wayerrors are handledin theQlik Reportingconnector forQlik Automate. The change was rolled out onAugust 12th,2025.
The following blocks will be replaced to facilitate the changes:
Get Chart Image
Get Pixel Perfect Report
Get Tabular Report
The functional change of the new blocks centers on error handling. While the old blocks output a simplefailedstring in case of an error, we wanted to update this output to include the full error object, including the status code and reason.
Additionally, in certain situations, the old blocks would have a successful run even though the output is an error; we updated this behavior so the new blocks will error out in any situation involving an error.
What does this mean for me?
The old blocks were renamed, flagging them as deprecated. Example: Get Chart Image (deprecated)
The new blocks retain the old names and are referenced in the description of the old blocks.
The action needed by Qlik Automate administrators and users is to switch from the (deprecated)blocks to the new ones.
If you have any questions, we're happy to assist. Reply to this blog post or take similar queries to theQlik Application Automation forum.
Thank you for choosing Qlik,Qlik Support
...View More
