CVE-2026-45108: himmelblau · Incorrect Authorization
Affects himmelblauSource CVE Database V5
Not known to be exploited · CVSS 8.4 High : upgrade to 3.1.5 or 2.3.11 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.1.5, 2.3.11
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade himmelblau to 3.1.5 or 2.3.11; himmelblau-idm/himmelblau to 2.3.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| himmelblau-idmhimmelblau | Affected
| Fixed in
|
| himmelblau-idmhimmelblau | Affected
| Fixed in
|
GitHubhimmelblau-idm/himmelblaupkg:github/himmelblau-idm/himmelblauOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability is fixed in himmelblau versions 2.3.11 and 3.1.5. Since himmelblau is a cloud service, the vendor manages remediation server-side. Users should verify with the vendor that their environment is running a patched version or that the vendor has applied the fix. Patch status is confirmed as available. No additional mitigation actions are specified or required beyond applying the official fix.
Description
Himmelblau versions from 2.0.0 up to but not including 2.3.11, and from 3.0.0-alpha up to but not including 3.1.5, contain an authentication bypass vulnerability in the Device Authorization Grant flow. This flaw allows a user within the same Microsoft Azure Entra ID domain to gain a local Unix session as another user by using their own valid credentials.