Key takeaways
- HID listed Reader Manager version 1.33.1 as a production release on August 25, 2026, with the status page using UTC for its timestamps.
- The stated scope is customer-reported fixes plus communications, stability and performance improvements in Signo, iCLASS and multiCLASS SE reader environments.
- HID did not publish itemized release notes, CVE references, or a claim that the update changes reader firmware.
- Administrators should pilot the mobile-app update with representative reader models, technician devices and workflows before fleet-wide deployment.
- The update is relevant to teams using Reader Manager for field configuration, key loading, settings changes or firmware-management tasks.
HID lists Reader Manager 1.33.1 as a production release
HID has posted version 1.33.1 of HID Reader Manager, its field-management tool for supported access-control readers. The manufacturer’s Origo Service Status page identifies the item as a production release announcement dated August 25, 2026, at 23:59 UTC. The status site states that its times are listed in UTC, so organizations scheduling work in U.S. time zones should translate the listed time before tying the event to a maintenance window.
HID characterizes the update as addressing customer-reported issues while improving reader communications, operational stability and overall performance. The announced scope specifically names HID Signo, HID iCLASS and HID multiCLASS SE reader environments.
What HID has — and has not — disclosed
The release notice provides a high-level change summary rather than itemized release notes. It does not identify individual defects, affected reader part numbers, mobile operating-system requirements, app-store build identifiers, vulnerability identifiers or reader-firmware revisions. It also does not describe the update as a security advisory or state that it remediates a specific cybersecurity issue.
That distinction matters for change-control teams. Reader Manager 1.33.1 should be treated as an operational software update whose benefits are described broadly by HID, not as a documented firmware or security-patch mandate. Sites with contractual maintenance, regulated change-control procedures or strict availability requirements should request any needed implementation detail from HID support before deployment.
Why the mobile-management workflow is affected
HID positions Reader Manager as a mobile application for managing supported readers in the field through Bluetooth. The product documentation describes functions including reader-firmware updates, loading HID Elite and mobile keys, enabling or disabling credential technologies, and changing reader audio-visual settings. An app-level update can therefore affect technician workflows even when no new reader firmware is being introduced.
For integrators, the relevant test is broader than whether the app launches. A pilot should cover the actual tasks performed at the customer site: technician sign-in, reader discovery, authorization and key access, configuration retrieval, approved configuration changes, and any firmware-related activity that is part of the maintenance plan. Record the Reader Manager version, phone or tablet model, mobile OS version, reader family and observed results.
Reader compatibility should be checked at the model level
HID’s Reader Manager product page identifies Signo readers, Bluetooth-capable iCLASS SE readers, Bluetooth-capable multiCLASS SE readers and iCLASS SE Express readers among compatible product groups. HID also directs users to its Reader Manager Solution Guide for detailed compatibility information. Compatibility should therefore not be inferred solely from a reader carrying an iCLASS SE or multiCLASS SE label.
HID lists the Signo Biometric Reader 25B and iCLASS SE RB25F as examples of readers that use HID Biometric Manager rather than Reader Manager. Before assigning 1.33.1 work to field technicians, administrators should compare their installed model list against HID’s compatibility documentation and confirm that the planned management path matches the equipment at each opening.
Recommended rollout approach for managed fleets
A practical deployment sequence is to update a small group of authorized technicians first, then test on a representative sample of noncritical doors. Include each reader family, communication method and credential configuration that is significant to the site. Where field firmware updates are routine, separate validation of the Reader Manager app from approval of any firmware package; HID’s release notice does not state that version 1.33.1 itself changes reader firmware.
Teams should also preserve the pre-change configuration and establish a clear stop point before working on high-traffic or security-sensitive openings. Confirm that credential reads, door transactions, reader indication behavior and management access remain normal after each test. A controlled rollout is particularly useful because HID’s published notice signals communications and stability improvements but does not enumerate the scenarios corrected.
Planning implication for access-control teams
Reader Manager 1.33.1 is a relevant maintenance item for organizations that use HID’s mobile workflow to administer deployed readers. The limited published detail supports a validation-first approach rather than an assumption that every installed reader or technician device will behave identically after the update.
For procurement and project teams, the release is also a reminder to keep accurate records of reader models, firmware levels, controller interfaces and the approved technician toolset. That inventory shortens compatibility checks and makes it easier to stage mobile-management changes alongside routine access-control service visits.
