How widely exploitable is this SSRF vulnerability?

Exploitability depends primarily on whether Docker Model Runner is configured to interact with untrusted or attacker-controlled OCI registries and whether it can reach internal services from its network position. In tightly controlled environments with only trusted registries and constrained egress, the practical risk is reduced, but the underlying flaw still warrants remediation.

Does an attacker need direct access to the host or Docker environment?

No direct host access is required. The attacker mainly needs control of a registry endpoint (or influence over which registry Model Runner uses) and a way to trigger model pulls so that the vulnerable token exchange flow executes.

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

The most robust fix is to introduce a strict validation and normalization layer for any remote URLs used in authentication or token exchange: - Only allow token service URLs that originate from configuration or a trusted mapping. - Enforce host and IP allowlists and block loopback, link-local, and private ranges where appropriate. - Treat all header-derived URLs as untrusted and subject them to centralized policy checks before making outbound requests.

Severity:

CRITICAL RISK

(9.1)

Server-Side Request Forgery (CWE-918) in Docker Model Runner OCI Registry Token Exchange

CVE-2026-33990

Published:

Apr 1, 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:

Server-Side Request Forgery (SSRF)

CWE:

CWE-918

Impact:

Internal network access and data exfiltration via SSRF

Severity:

CRITICAL RISK

(9.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Server-Side Request Forgery (SSRF)

CWE:

CWE-918

Impact:

Internal network access and data exfiltration via SSRF

Severity:

CRITICAL RISK

(9.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 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 (CWE-918) in Docker Model Runner OCI Registry Token Exchange

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