CVE-2026-58422
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper authorization on OAuth sign-in callback silently re-enables administrator-disabled accounts
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe OAuth sign-in callback endpoint lacks proper authorization validation, allowing the authentication flow to complete and re-enable user accounts that administrators have previously disabled. When a disabled user authenticates via OAuth, the system improperly creates or updates their session without checking account status.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OAuth authentication configurationReview system authentication settings or configuration files to determine if OAuth-based sign-in is enabled. Look for OAuth provider configurations, callback URLs, or authentication method settings.Affected if OAuth sign-in is enabled and in use
-
Locate OAuth callback endpoint logsAccess authentication or security logs and search for OAuth callback events. Filter for entries containing 'callback', 'OAuth', 'authenticate', or similar terms related to sign-in flow.Affected if OAuth callback requests are being processed by the system
-
Verify account status validation in authentication flowReview the OAuth callback handler code or configuration to determine if account status (enabled/disabled) is checked before creating a session. Look for authorization or account validation logic in the authentication pipeline.Affected if No account status check exists before session creation in OAuth flow
-
Test authentication with a disabled user accountIf permitted in your environment, attempt OAuth sign-in using an account that has been explicitly disabled in the user directory or admin panel. Observe whether authentication succeeds and a session is created.Affected if Disabled user can successfully complete OAuth authentication and obtain a session
A user is affected if OAuth sign-in is enabled and the system allows disabled users to authenticate and obtain a session without verifying account status in the OAuth callback handler.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement authorization checks in OAuth callback handlers to verify the account is still active and not disabled before establishing a session or completing authentication.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58422 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58422 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data