Is this vulnerability remotely exploitable over the public internet?

It can be, provided an attacker either controls the configured upstream registry or can position themselves as a man-in-the-middle on the connection between Distribution and the upstream. In such cases, they can craft WWW-Authenticate challenges that redirect credential-bearing requests to their own infrastructure.

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

The attacker must be able to influence responses from the upstream registry—either by operating that registry, compromising it, or intercepting and modifying network traffic en route. They do not need direct access to the Distribution service itself to trigger the flaw.

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

The core fix pattern is to validate and constrain any dynamically discovered URLs before use. Specifically, ensure that bearer realm or similar discovery URLs are restricted to the expected upstream host (or a strict allowlist) and reject any challenges that reference untrusted domains or schemes. Combine this with least-privilege credential configurations so that, even if a validation gap remains, credential exposure risk is reduced.

Severity:

HIGH RISK

(7.5)

Server-Side Request Forgery in Token Auth Discovery (CWE-918) for Container Distribution Pull-Through Cache

CVE-2026-33540

Published:

Apr 6, 2026

Status:

Received

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:

Server-Side Request Forgery (SSRF) / Insecure Authentication Endpoint Discovery

CWE:

CWE-918

Impact:

Credential Exfiltration via Server-Side Request Forgery

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Vulnerability Type

Category:

Server-Side Request Forgery (SSRF) / Insecure Authentication Endpoint Discovery

CWE:

CWE-918

Impact:

Credential Exfiltration via Server-Side Request Forgery

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

Server-Side Request Forgery in Token Auth Discovery (CWE-918) for Container Distribution Pull-Through Cache

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