How severe is CVE-2026-62874?

CVE-2026-62874 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability low.

Is CVE-2026-62874 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (25th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-62874?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2026-62874 published?

CVE-2026-62874 was published on 2026-09-18 and last updated on 2026-09-19.

CVE-2026-62874

CVE-2026-62874 is a critical-severity vulnerability with a CVSS 3.x base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-345.

Key facts

Severity: Critical (CVSS 3.x base score 10.0)
EPSS exploit prediction: 0% (25th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-345
Published: 2026-09-18
Last modified: 2026-09-19

Description

Insufficient verification of data authenticity in Azure Billing allows an unauthorized attacker to elevate privileges over a network.

Frequently asked questions

What is CVE-2026-62874?: Insufficient verification of data authenticity in Azure Billing allows an unauthorized attacker to elevate privileges over a network.
How severe is CVE-2026-62874?: CVE-2026-62874 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability low.
Is CVE-2026-62874 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (25th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-62874?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-62874 published?: CVE-2026-62874 was published on 2026-09-18 and last updated on 2026-09-19.

References

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62874

Other CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities

CVE-2026-35051 — Critical (CVSS 10.0): Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is an…
CVE-2014-8165 — Critical (CVSS 10.0): scripts/amsvis/powerpcAMS/amsnet.py in powerpc-utils-python uses the pickle Python module unsafely, which allows remote…
CVE-2026-50195 — Critical (CVSS 9.9): containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a vulnerability in the…
CVE-2022-36130 — Critical (CVSS 9.9): HashiCorp Boundary up to 0.10.1 did not properly perform data integrity checks to ensure the resources were associated…
CVE-2026-80172 — Critical (CVSS 9.8): Dell SCG 5.0 Appliance versions prior to 5.36.00.16 and Dell SCG 5.0 Application versions prior to 5.36.00.00, contains…
CVE-2026-82858 — Critical (CVSS 9.8): @hulumi/drift versions before 1.3.2 accept externally supplied execute plans without sufficient provenance validation,…

Browse all CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities →