Is this vulnerability remotely exploitable over the network?

It typically requires access to the victim's browser environment, such as through a compromised user account, local access, or malicious extensions. However, once an attacker can see the client runtime, extracting visible API keys becomes straightforward.

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

An attacker generally needs the ability to inspect or control the browser running the application—using developer tools, injected JavaScript, or other mechanisms that can read client-side state and logs.

What is the safest general fix pattern for this vulnerability?

The most robust fix is to remove long-lived secrets from the client entirely, keep master keys on the server, and rely on short-lived, scoped tokens or session-based authorization that never exposes raw credentials to the browser.

Severity:

HIGH RISK

(7.5)

Insufficiently Protected Credentials (CWE-522) in Temporary Browser Client Storage

CVE-2026-35467

Published:

Apr 2, 2026

Status:

Awaiting Analysis

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-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

Remote Code Execution on the Router

April 6, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Remote Code Execution on Router Firmware

April 6, 2026

Vulnerability Type

Category:

Insufficiently Protected Credentials

CWE:

CWE-522

Impact:

Credential Exposure and Unauthorized API Access

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Vulnerability Type

Category:

Insufficiently Protected Credentials

CWE:

CWE-522

Impact:

Credential Exposure and Unauthorized API Access

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

Insufficiently Protected Credentials (CWE-522) in Temporary Browser Client Storage

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)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

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