CVE-2026-111823: Critical severity Mage Mage OSS vulnerability
Mage OSS through 0.9.80 before 76c4f46 can proceed with session creation upon encountering an unknown OAuth provider.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Mage OSSto a version that resolves this vulnerability.Patch PR #6204 (4fc5e1860260c4f772d852a28323eb65405178df) - Upgrade
Upgrade
Mage OSSto a version that resolves this vulnerability.Patch PR #6205 (4a8904fcd2765859bd4e2b87fb284dabddb13c83) - Upgrade
Upgrade
Mage OSSto a version that resolves this vulnerability.Patch PR #6207 (9c6331991c5e6e43d755bd59c151864ef28fdc11)
Event History
Frequently Asked Questions
Who can exploit this issue?
The CVSS vector indicates network-based exploitation with low attack complexity, no required privileges, and no user interaction. An unauthenticated remote attacker can trigger the affected OAuth-provider handling path.
Which deployments are affected?
Mage OSS versions through 0.9.80 are affected if they do not include commit 76c4f46. The issue occurs when Mage encounters an unknown OAuth provider.
What should teams do if they cannot patch immediately?
The provided data does not identify a workaround. Prioritize restricting network access to the affected Mage OSS instance and avoid configurations or requests that allow unknown OAuth providers to reach session-creation handling.
How can we determine whether our instance is remediated?
Verify that the deployed Mage OSS code includes commit 76c4f46 or a later version containing that change. Versions through 0.9.80 without that commit are affected.