How do I check whether I am affected by CVE-2026-111823?

Run 'pip show mage-ai' (or check the Docker image tag). Version 0.9.80 or older, without commit 76c4f46, is affected. Check whether the Mage UI/API is reachable by untrusted networks. Whether it matters when OAuth is not configured is unconfirmed.

What is the fix for CVE-2026-111823?

No release containing 76c4f46 found yet (latest is 0.9.80). Build from the mage-ai/mage-ai repo at 76c4f467f3654041d8899b1c4447a985710d26c0 or later, or upgrade once a release after 0.9.80 ships. Until then, do not expose Mage to untrusted networks (put it behind a VPN or authenticated proxy).

Who is not affected by CVE-2026-111823?

Not affected if: not-internet-exposed, unknown.

Live › vulnerability › CVE-2026-111823

Go to dashboard

critical9.8Other

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

Mage OSS up to 0.9.80 (the latest release as of 23 Oct 2026) can create a login session from an unverified OAuth provider/token in the session-create API, so an unauthenticated attacker may get a session. The fix is commit 76c4f46 on master, and no release containing it was found.

Summary written from the sources below. Check the originals before acting.

CVSS 3.x

9.8

critical

scored by [email protected]

known so far5 of 6

missing: exploitation

First public: Oct 17, 2026 UTC
Last modified: Oct 23, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is critical, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: No.
Needs a special setup: Not known from the sources.
Reachable from: Not known from the sources.
Worst case: Attacker obtains a session as a user without valid credentials.
CVSS said: 9.8. The facts above say high; we keep the sources' critical until an analyst looks.

Who is affected

1 product

Know the next one before it finds you.

Add to Slack

Live › vulnerability › CVE-2026-111823

Go to dashboard

critical9.8Other

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

Summary written from the sources below. Check the originals before acting.

CVSS 3.x

9.8

critical

scored by [email protected]

known so far5 of 6

missing: exploitation

First public: Oct 17, 2026 UTC
Last modified: Oct 23, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.

Why it is critical, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: No.
Needs a special setup: Not known from the sources.
Reachable from: Not known from the sources.
Worst case: Attacker obtains a session as a user without valid credentials.
CVSS said: 9.8. The facts above say high; we keep the sources' critical until an analyst looks.

Who is affected

1 product

Know the next one before it finds you.

Add to Slack

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

Why it is critical, and not just CVSS

Who is affected

Know the next one before it finds you.

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

Why it is critical, and not just CVSS

Who is affected

Know the next one before it finds you.

How to check

The fix

Who had it, and when

What the sources say, verbatim

Sources