Resolved Issues - Jamf Pro Release Notes 11.33.0

Jamf Pro Release Notes 11.33.0
Solution
Application
Content Type
Technical Documentation
Release Notes
Utilities & Services
version
11.33.0
ft:locale
en-US
vrm_version
11.33.0

Note:

Some resolved issues in this release may have been addressed in a previous maintenance release.

Jamf Pro Server: Security Issues

Jamf provides the CVE-ID for security issues with high or critical severity when possible.

  • [PI201341] Fixed: A denial-of-service issue.

  • [PI205277] Fixed: A known vulnerability in a third-party library (CVE-2026-59888).

  • [PI205872] Fixed: A known vulnerability in a third-party library (CVE-2026-56822, CVE-2026-55831, CVE-2026-59901).

  • [PI205880] Fixed: A known vulnerability in a third-party library (CVE-2026-10050).

  • [PI212062] Fixed: A known vulnerability in a third-party library (CVE-2026-69153).

  • [PI217394] Fixed: A known vulnerability in a third-party library (CVE-2026-54428).

  • [PI217449] Fixed: A known vulnerability in a third-party library (CVE-2026-67213).

  • [PI217488] Fixed: A known vulnerability in a third-party library (CVE-2026-73646).

  • [PI220987] Fixed: A known vulnerability in a third-party library (CVE-2026-69151).

  • [PI220994] Fixed: A known vulnerability in a third-party library (CVE-2026-68945).

  • [PI222752] Fixed: A known vulnerability in a third-party library (CVE-2026-55858).

  • [PI223203] Fixed: A known vulnerability in a third-party library (CVE-2026-73089).

  • [PI-1654] [PI223696] Fixed: A known vulnerability in a third-party library (CVE-2026-41003).

  • [PI228084] Fixed: An input validation issue in the Jamf Pro API.

  • [PI229326] Fixed: A known vulnerability in a third-party library (CVE-2026-8763).

  • [PI230592] Fixed: A privilege escalation issue in the Jamf Pro API.

Jamf Pro Server

  • [PI-79] [PI102023] [PI-007813] Fixed: Viewing the full list of configuration profiles in the Configuration Profiles overview or the Jamf Pro Dashboard may cause performance issues.

  • [PI-220] [PI110880] Fixed: When editing a policy with the deferral date setting configured, Jamf Pro repeatedly adjusts the value for UTC each time the policy is edited and saved.

  • [PI-908] Fixed: The device-level "Enforce Mobile Device Name" option in Inventory > General settings takes priority over the Naming Method specified in Mobile devices > PreStage enrollments > Options > Mobile Device Name. Devices that are re-enrolled and moved to a new PreStage enrollment that has a different naming method retain the device-level name defined during their previous enrollments.

  • [PI-1519] Fixed: Jamf Pro returns a 409 error when using referential smart groups with the advanced mobile device searches API endpoint.

  • [PI-1535] Fixed: The Send Remote Commands mass action for mobile devices takes longer than expected to resolve for large groups.

  • [PI-1566] Fixed: Smart group updates may fail to refresh group membership when edited and saved repeatedly in quick succession.

  • [PI-1580] Fixed: The device compliance workflow with Entra ID fails to register devices if an interactive sign-in option (such as multifactor authentication) is enabled.

  • [PI-1592] Fixed: Volume purchase invitations sent to users with personal Apple Accounts do not display device-level prompts or appear in Self Service classic for mobile, preventing users from associating their accounts and receiving assigned content.
    Important:

    The change in [PI-1592] applies only to volume purchase invitations sent after you upgrade. Invitations that were already pending before the upgrade remain pending and are not resolved automatically. To resolve a pending invitation, send a new invitation to the affected user.

  • [PI-1618] [PI221593] Fixed: The identity first workflow with Platform SSO fails with a 409 "Ambiguous SSO provider" error when the Okta profile's AppPrefixAllowList contains com.microsoft.

  • [PI-1724] Fixed: Managed computers without an MDM profile fail to download and install packages hosted on the Jamf Cloud Distribution Service (JCDS).

  • [PI184900] Fixed: The /api/v3/computer-groups/smart-groups endpoint rejects the "has" and "does not have" operators for LDAP multi-value extension attribute criteria, even though the Jamf Pro interface uses these operators successfully. The API accepts "like" and "not like" instead, but these render incorrectly as "has" in the interface.

  • [PI191837] Fixed: eBook deployment operations trigger unnecessary database updates to certificate data for all devices in scope, even when no certificate changes have occurred. This can exhaust the database connection pool during large-scale deployments.