CVE-2025-54882
Himmelblau-idm Himmelblau vulnerability
- Published6 Aug 2025
Description
Himmelblau is an interoperability suite for Microsoft Azure Entra ID and Intune. In versions 0.8.0 through 0.9.21 and 1.0.0-beta through 1.1.0, Himmelblau stores the cloud TGT received during logon in the Kerberos credential cache. The created credential cache collection and received credentials are stored as world readable. This is fixed in versions 0.9.22 and 1.2.0. To work around this issue, remove all read access to Himmelblau caches for all users except for owners.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NAffected products
Remediation
References
- https://github.com/himmelblau-idm/himmelblau/commit/b562053df3dffb1dd9ab3d09af986886773be2ad
- https://github.com/himmelblau-idm/himmelblau/commit/faae58b0384aca8b21b4be5f1c507412eec3778a
- https://github.com/himmelblau-idm/himmelblau/releases/tag/0.9.22
- https://github.com/himmelblau-idm/himmelblau/releases/tag/1.2.0
- https://github.com/himmelblau-idm/himmelblau/security/advisories/GHSA-phfx-rjfw-wj83
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-54882 being actively exploited?
CVE-2025-54882 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.22%.
How severe is CVE-2025-54882?
CVE-2025-54882 has a CVSS 3.1 base score of 7.1, rated high. EPSS estimates a 0.22% probability of exploitation.
Which products are affected by CVE-2025-54882?
Affected products include Himmelblau-idm Himmelblau.
How do I fix CVE-2025-54882?
Upgrade affected software to a fixed version, for example Himmelblau-idm Himmelblau 0.9.22 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-54882 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.