How broadly exploitable is this vulnerability?

Exploitation is generally limited to parties who can access environments that record URLs or Referer headers—such as server operators, infrastructure providers, monitoring tools, or anyone with access to end-user browser history. It is not a direct remote vulnerability where arbitrary attackers can simply send a crafted request and obtain tokens.

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

An attacker would need read access to logs, analytics data, or browser history that includes the affected OAuth callback URLs. This could mean compromised operations accounts, abused integrations with third-party observability services, malware on user devices, or unauthorized access to internal logging systems.

What is the safest general fix pattern for this class of issue?

The most robust fix is to completely avoid placing any sensitive tokens or credentials in URLs. Instead, use secure, server-controlled mechanisms: HTTP-only cookies, backchannel token exchanges, or POST-based flows. Additionally, ensure that logging and observability systems are configured to avoid storing secrets, even if a coding mistake occurs.

Severity:

HIGH RISK

(7.5)

Sensitive Refresh Token Exposure via URL Parameters (CWE-598, CWE-200) in Nhost Auth OAuth Callback

CVE-2026-34969

Published:

Apr 6, 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-74;CWE-89

HIGH RISK

HIGH

(7.3)

SQL Injection via Unsanitized ID Parameter (CWE-89) in Pharmacy Sales and Inventory System /ajax.php

Database Compromise and Data Integrity Loss

April 27, 2026

CWE-863

HIGH RISK

HIGH

(8.5)

Incorrect Authorization (CWE-863) in OpenClaw chat.send Session Management

Privilege Escalation and Unauthorized Session Control

April 27, 2026

Vulnerability Type

Category:

Sensitive Information Exposure via URL

CWE:

CWE-200;CWE-598

Impact:

Account Takeover / Session Hijacking via Token Leakage

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Vulnerability Type

Category:

Sensitive Information Exposure via URL

CWE:

CWE-200;CWE-598

Impact:

Account Takeover / Session Hijacking via Token Leakage

Severity:

HIGH RISK

(7.5)

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 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Sensitive Refresh Token Exposure via URL Parameters (CWE-598, CWE-200) in Nhost Auth OAuth Callback

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

(7.3)

SQL Injection via Unsanitized ID Parameter (CWE-89) in Pharmacy Sales and Inventory System /ajax.php

HIGH RISK

HIGH

(8.5)

Incorrect Authorization (CWE-863) in OpenClaw chat.send Session Management

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare