Secuno
ENNL
Book demo

CVE-2026-48567

Microsoft Azure Horizondb authentication bypass

10.0 CRITICALEPSS 0.92%
  1. Published4 Jun 2026

Description

Authentication bypass by spoofing in Azure HorizonDB allows an unauthorized attacker to elevate privileges over a network.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeChanged
ConfidentialityNone
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H

Affected products

Microsoft Azure Horizondball versions

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-935829.4
The HTTP Basic Authentication modules in ((OTRS)) Community Edition 6 and prior accept…
CVE-2026-1021618.8
An unauthenticated attacker located on an adjacent private network (or any attacker…
CVE-2026-1056409.1
Plane is an open-source project management tool. Prior to 1.4.0, Plane trusts email…
CVE-2026-1052159.1
ZITADEL before 3.4.14 and 4.x before 4.16.2 contains an authentication bypass in the…
CVE-2026-1049888.1
A flaw was found in Dogtag PKI (pki-core). The CMCAuthForEST authentication plugin…
CVE-2026-944228.8
An incorrect implementation of message filtering in xdg-dbus-proxy versions before…

Frequently asked

Is CVE-2026-48567 being actively exploited?

CVE-2026-48567 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.92%.

How severe is CVE-2026-48567?

CVE-2026-48567 has a CVSS 3.1 base score of 10.0, rated critical. EPSS estimates a 0.92% probability of exploitation.

Which products are affected by CVE-2026-48567?

Affected products include Microsoft Azure Horizondb.

How do I fix CVE-2026-48567?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-48567 against the real software inventory on every managed device, as each hourly inventory arrives. 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.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.