Today we are releasing a maintenance version of Jamf Pro; this release addresses the following product issues:
Jamf Pro Server: Security Issues
Jamf provides the CVE-ID for security issues with high or critical severity when possible.
[PI126232] Updated a third-party library to resolve a known vulnerability. (CVE-2025-24970)
Jamf Pro Server
- [PI125880] Jamf Pro users who migrated from an on-premise environment to a Jamf Standard Cloud-hosted or Premium Cloud-hosted environment using a custom URL and port 8443 will no longer experience authentication errors while using SSO through Jamf Account.
- [PI126314] Jamf Pro successfully populates data in the mdm_client database table, resolving an issue that prevented computers from receiving user-level commands and configuration profiles.
- [PI133965] Jamf Pro users in on-premise environments will no longer see reminders to enable single sign-on (SSO) through Jamf Account, which is only available in cloud-hosted environments.
Jamf Pro System Requirements: Update
MySQL 8.0.41 is now supported and recommended as a database configuration for on-premise environments.
For additional information on what's included in this release, review the release notes via the Jamf Learning Hub.
To access new versions of Jamf Pro, log into Jamf Account with your Jamf ID. The latest version is located in the Solutions section under Jamf Pro.
Cloud Upgrade Schedule
Your Jamf Pro server, including any free sandbox environments, will be updated based on your hosted data region below. Review this guide if you need assistance identifying the Hosted Data Region of your Jamf Cloud instance.
If you would like to upgrade manually, log in to Jamf Account and select Jamf Pro Info >; click Upgrade on the appropriate instance. Note: This capability is not available for GovCloud environments and is disabled for all instances one day prior to when the scheduled standard upgrades begin.
Subscribe to product alerts to receive real-time updates.
| Hosted Region |
Begins |
Ends |
| ap-southeast-2 |
28 February at 1300 UTC |
28 February at 1900 UTC |
| ap-northeast-1 |
28 February at 1500 UTC |
28 February at 2300 UTC |
| eu-central-1 |
28 February at 2300 UTC |
1 March at 1000 UTC |
| eu-west-2 |
1 March at 0000 UTC |
1 March at 0700 UTC |
| us-east-2 |
1 March at 0500 UTC |
1 March at 1500 UTC |
| us-west-2 |
1 March at 0800 UTC |
1 March at 1900 UTC |
