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.
[PI124081] Fixed: A known vulnerability in a third-party library. (CVE-2024-47554)
Jamf Pro Server
- [PI135204] Fixed: After device re-enrollment, some configuration profiles may fail to install automatically even when properly scoped to the device.
- [PI135884] Fixed: Smart user groups that use excluding criteria (e.g., "is not", "not like", "does not match regex") to match roster data fail to match users with no associated Apple School Manager roster data due to a smart group calculation error.
- [PI135942] Fixed: An update to Log4j introduced a threading issue that could cause silent thread failures during server operations.
- [PI135944] Fixed: When "Last Reported IP Address" is selected as a display field for an advanced computer search, the display field fails to appear in the results.
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.
| Region |
Begins |
Ends |
| ap-southeast-2 |
30 May at 1400 UTC |
30 May at 2000 UTC |
| ap-northeast-1 |
30 May at 1500 UTC |
30 May at 2300 UTC |
| eu-central-1 |
30 May at 2200 UTC |
31 May at 0900 UTC |
| eu-west-2 |
30 May at 2300 UTC |
31 May at 0600 UTC |
| us-east-2 |
31 May at 0400 UTC |
31 May at 1400 UTC |
| us-west-2 |
31 May at 0700 UTC |
31 May at 1800 UTC |
