Is this vulnerability remotely exploitable?

Yes. An attacker can remotely exploit this issue by crafting a malicious authorization URL and tricking users into visiting it. No direct network access to the server beyond normal web access is required.

What level of access does an attacker need to exploit it?

The attacker does not need authenticated access to the OIDC provider itself; they primarily need the ability to deliver a crafted `redirect_uri` authorization link to a victim (for example via phishing emails, malicious websites, or injected links in existing applications).

What is the safest general fix pattern for developers?

The safest pattern is to enforce strict, parser-based validation of `redirect_uri` values against a pre-registered allowlist per client, rejecting any URLs that do not exactly match or that contain unexpected components like userinfo or unsupported schemes.

Severity:

HIGH RISK

(7.1)

Open Redirect via Userinfo in Callback URL Validation (CWE-601) in Pocket ID OIDC Provider

CVE-2026-28512

Published:

Mar 10, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Open Redirect / Unvalidated Redirects

CWE:

CWE-601

Impact:

Authorization Code / Token Theft via Open Redirect

Severity:

HIGH RISK

(7.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Open Redirect / Unvalidated Redirects

CWE:

CWE-601

Impact:

Authorization Code / Token Theft via Open Redirect

Severity:

HIGH RISK

(7.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Open Redirect via Userinfo in Callback URL Validation (CWE-601) in Pocket ID OIDC Provider

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal