How severe is CVE-2026-111823?

CVE-2026-111823 has a CVSS 3.x base score of 9.8, 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 high.

Is CVE-2026-111823 being actively exploited?

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

How do I fix CVE-2026-111823?

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-111823 published?

CVE-2026-111823 was published on 2026-10-17 and last updated on 2026-10-19.

CVE-2026-111823

CVE-2026-111823 is a critical-severity vulnerability with a CVSS 3.x base score of 9.8. 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-390.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
EPSS exploit prediction: 0% (30th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-390
Published: 2026-10-17
Last modified: 2026-10-19

Description

Mage OSS through 0.9.80 before 76c4f46 can proceed with session creation upon encountering an unknown OAuth provider.

Frequently asked questions

What is CVE-2026-111823?: Mage OSS through 0.9.80 before 76c4f46 can proceed with session creation upon encountering an unknown OAuth provider.
How severe is CVE-2026-111823?: CVE-2026-111823 has a CVSS 3.x base score of 9.8, 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 high.
Is CVE-2026-111823 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (30th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-111823?: 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-111823 published?: CVE-2026-111823 was published on 2026-10-17 and last updated on 2026-10-19.

References

Other CWE-390 vulnerabilities

CVE-2026-43493 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: crypto: pcrypt - Fix handling of MAY_BACKLOG…
CVE-2026-104480 — Critical (CVSS 9.4): Discord libdave before 1.2.0 did not reject an MLS Welcome message when the resulting group roster contained an…
CVE-2026-53434 — Critical (CVSS 9.1): Detection of Error Condition Without Action vulnerability in Apache Tomcat when configuring CRLs for a FFM based…
CVE-2026-76642 — High (CVSS 7.8): util-linux versions through 2.41.5 and 2.42.2 fail to check mount helper exit status before running post-mount hooks,…
CVE-2025-46367 — High (CVSS 7.8): Dell Alienware Command Center 6.x (AWCC), versions prior to 6.10.15.0, contain a Detection of Error Condition Without…
CVE-2024-27919 — High (CVSS 7.5): Envoy is a cloud-native, open-source edge and service proxy. In versions 1.29.0 and 1.29.1, theEnvoy HTTP/2 protocol…

Browse all CWE-390 vulnerabilities →