himmelblau up to 0.9.16 himmelblau.conf acquire_token_by_hello_for_business_key improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 1.40 |
Summary
A vulnerability was found in himmelblau up to 0.9.16. It has been classified as critical. This affects the function acquire_token_by_hello_for_business_key of the file /etc/himmelblau/himmelblau.conf. Performing a manipulation results in improper authentication.
This vulnerability is known as CVE-2025-53013. The attack may be carried out on the physical device. No exploit is available.
Upgrading the affected component is recommended.
Details
A vulnerability was found in himmelblau up to 0.9.16. It has been classified as critical. This affects the function acquire_token_by_hello_for_business_key of the file /etc/himmelblau/himmelblau.conf. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Himmelblau is an interoperability suite for Microsoft Azure Entra ID and Intune. A vulnerability present in versions 0.9.10 through 0.9.16 allows a user to authenticate to a Linux host via Himmelblau using an *invalid* Linux Hello PIN, provided the host is offline. While the user gains access to the local system, Single Sign-On (SSO) fails due to the network being down and the inability to issue tokens (due to a failure to unlock the Hello key). The core issue lies in an incorrect assumption within the `acquire_token_by_hello_for_business_key` function: it was expected to return a `TPMFail` error for an invalid Hello key when offline, but instead, a preceding nonce request resulted in a `RequestFailed` error, leading the system to erroneously transition to an offline success state without validating the Hello key unlock. This impacts systems using Himmelblau for authentication when operating in an offline state with Hello PIN authentication enabled. Rocky Linux 8 (and variants) are not affected by this vulnerability. The problem is resolved in Himmelblau version 0.9.17. A workaround is available for users who cannot immediately upgrade. Disabling Hello PIN authentication by setting `enable_hello = false` in `/etc/himmelblau/himmelblau.conf` will mitigate the vulnerability.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-53013 since 06/24/2025. The exploitability is told to be easy. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 306681 (SUSE SLED15 / SLES15 Security Update : himmelblau (SUSE-SU-2026:1361-1)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 0.9.17 eliminates this vulnerability. Applying the patch 64b03739f1d5ee472b1cff3ed20ed9af1c65a6f8 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (306681) and EUVD (EUVD-2025-19217). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.6
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.2
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: Yes
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 306681
Nessus Name: SUSE SLED15 / SLES15 Security Update : himmelblau (SUSE-SU-2026:1361-1)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: himmelblau 0.9.17
Patch: 64b03739f1d5ee472b1cff3ed20ed9af1c65a6f8
Timeline
06/24/2025 CVE reserved06/26/2025 Advisory disclosed
06/26/2025 VulDB entry created
04/17/2026 VulDB entry last update
Sources
Advisory: GHSA-j93j-pwm6-p97jStatus: Confirmed
CVE: CVE-2025-53013 (🔒)
GCVE (CVE): GCVE-0-2025-53013
GCVE (VulDB): GCVE-100-314025
EUVD: 🔒
Entry
Created: 06/26/2025 21:58Updated: 04/17/2026 00:58
Changes: 06/26/2025 21:58 (67), 06/27/2025 03:03 (1), 08/21/2025 01:35 (1), 04/17/2026 00:58 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.